<!DOCTYPE html>
<html lang="en"><head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <title>Versioning Extensions to WebDAV (Web&nbsp;Distributed&nbsp;Authoring&nbsp;and&nbsp;Versioning)</title><script type="application/javascript">
function getMeta(rfcno, container) {

  var xhr = new XMLHttpRequest();
  xhr.open("GET", "https://tools.ietf.org/draft/rfc" + rfcno + "/state.xml", true);
  xhr.onload = function (e) {
    if (xhr.readyState === 4) {
      if (xhr.status === 200) {
        var doc = xhr.responseXML;
        var info = getChildByName(doc.documentElement, "info");
  
        var cont = document.getElementById(container);
        // empty the container
        while (cont.firstChild) {
          cont.removeChild(myNode.firstChild);
        }      
  
        var c = getChildByName(info, "stdstatus");
        if (c !== null) {
          var bld = newElementWithText("b", c.textContent);
          cont.appendChild(bld);
        }
  
        c = getChildByName(info, "updatedby");
        if (c !== null) {
          cont.appendChild(newElement("br"));
          cont.appendChild(newText("Updated by: "));
          appendRfcLinks(cont, c.textContent);
        }
  
        c = getChildByName(info, "obsoletedby");
        if (c !== null) {
          cont.appendChild(newElement("br"));
          cont.appendChild(newText("Obsoleted by: "));
          appendRfcLinks(cont, c.textContent);
        }
        
        c = getChildByName(info, "errata");
        if (c !== null) {
          cont.appendChild(newElement("br"));
          var link = newElementWithText("a", "errata");
          link.setAttribute("href", "http://www.rfc-editor.org/errata_search.php?rfc=" + rfcno);
          var errata = newElementWithText("i", "This document has ");
          errata.appendChild(link);
          errata.appendChild(newText("."));
          cont.appendChild(errata);
        }

        cont.style.display = "block";
      } else {
        console.error(xhr.statusText);
      }
    }
  };
  xhr.onerror = function (e) {
    console.error(xhr.status + " " + xhr.statusText);
  };
  xhr.send(null);
}

// DOM helpers
function newElement(name) {
  return document.createElement(name);
}
function newElementWithText(name, txt) {
  var e = document.createElement(name);
  e.appendChild(newText(txt));
  return e;
}
function newText(text) {
  return document.createTextNode(text);
}

function getChildByName(parent, name) {
  if (parent === null) {
    return null;
  }
  else {
    for (var c = parent.firstChild; c !== null; c = c.nextSibling) {
      if (name == c.nodeName) {
        return c;
      }
    }
    return null;
  }
}

function appendRfcLinks(parent, text) {
  var updates = text.split(",");
  for (var i = 0; i < updates.length; i++) {
    var rfc = updates[i].trim();
    if (rfc.substring(0, 3) == "rfc") {
      var link = newElement("a");
      link.setAttribute("href", "http://tools.ietf.org/html/" + rfc);
      link.appendChild(newText(rfc.substring(3)));
      parent.appendChild(link);
    } else {
      parent.appendChild(newText(rfc));
    }
    if (i != updates.length - 1) {
      parent.appendChild(newText(", "));
    }
  }
}
</script><script type="application/javascript">
function anchorRewrite() {
  map = { };
  if (window.location.hash.length >= 1) {
    var fragid = window.location.hash.substr(1);
    if (fragid) {
      if (! document.getElementById(fragid)) {
        var prefix = "rfc.";
        var mapped = map[fragid];
        if (mapped) {
          window.location.hash = mapped;
        } else if (fragid.indexOf("section-") == 0) {
          window.location.hash = prefix + "section." + fragid.substring(8);
        } else if (fragid.indexOf("appendix-") == 0) {
          window.location.hash = prefix + "section." + fragid.substring(9);
        } else if (fragid.indexOf("s-") == 0) {
          window.location.hash = prefix + "section." + fragid.substring(2);
        } else if (fragid.indexOf("p-") == 0) {
          var r = fragid.substring(2);
          var p = r.indexOf("-");
          if (p >= 0) {
            window.location.hash = prefix + "section." + r.substring(0, p) + ".p." + r.substring(p + 1);
          }
        }
      }
    }  
  }
}
window.addEventListener('hashchange', anchorRewrite);
window.addEventListener('DOMContentLoaded', anchorRewrite);
</script><style type="text/css" title="Xml2Rfc (sans serif)">
a {
  text-decoration: none;
}
a.smpl {
  color: black;
}
a:hover {
  text-decoration: underline;
}
a:active {
  text-decoration: underline;
}
address {
  margin-top: 1em;
  margin-left: 2em;
  font-style: normal;
}
body {
  color: black;
  font-family: cambria, georgia, serif;
  font-size: 12pt;
  margin: 2em auto;
  max-width: 1000px;
}
samp, span.tt, code, pre {
  font-family: consolas, monaco, monospace;
}
cite {
  font-style: normal;
}
dl {
  margin-left: 2em;
}
dl > dt {
  float: left;
  margin-right: 1em;
}
dl.nohang > dt {
  float: none;
}
dl > dd {
  margin-bottom: .5em;
}
dl.compact > dd {
  margin-bottom: .0em;
}
dl > dd > dl {
  margin-top: 0.5em;
}
ul.empty {
  list-style-type: none;
}
ul.empty li {
  margin-top: .5em;
}
dl p {
  margin-left: 0em;
}
dl.reference > dt {
  font-weight: bold;
}
dl.reference > dd {
  margin-left: 6em;
}
h1 {
  color: green;
  font-size: 150%;
  line-height: 18pt;
  font-weight: bold;
  text-align: center;
  margin-top: 36pt;
  margin-bottom: 0pt;
}
h2 {
  font-size: 130%;
  line-height: 21pt;
  page-break-after: avoid;
}
h2.np {
  page-break-before: always;
}
h3 {
  font-size: 120%;
  line-height: 15pt;
  page-break-after: avoid;
}
h4 {
  font-size: 110%;
  page-break-after: avoid;
}
h5, h6 {
  page-break-after: avoid;
}
h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
  color: black;
}
img {
  margin-left: 3em;
}
li {
  margin-left: 2em;
}
ol {
  margin-left: 2em;
}
ol.la {
  list-style-type: lower-alpha;
}
ol.ua {
  list-style-type: upper-alpha;
}
ol p {
  margin-left: 0em;
}
p {
  margin-left: 2em;
}
pre {
  font-size: 11pt;
  margin-left: 3em;
  background-color: lightyellow;
  padding: .25em;
  page-break-inside: avoid;
}
pre.text2 {
  border-style: dotted;
  border-width: 1px;
  background-color: #f0f0f0;
}
pre.inline {
  background-color: white;
  padding: 0em;
  page-break-inside: auto;
}
pre.text {
  border-style: dotted;
  border-width: 1px;
  background-color: #f8f8f8;
}
pre.drawing {
  border-style: solid;
  border-width: 1px;
  background-color: #f8f8f8;
  padding: 2em;
}
table {
  margin-left: 2em;
}
table.header {
  border-spacing: 1px;
  width: 95%;
  font-size: 11pt;
  color: white;
}
td.top {
  vertical-align: top;
}
td.topnowrap {
  vertical-align: top;
  white-space: nowrap;
}
table.header td {
  background-color: gray;
  width: 50%;
}
ul.toc, ul.toc ul {
  list-style: none;
  margin-left: 1.5em;
  padding-left: 0em;
}
ul.toc li {
  line-height: 150%;
  font-weight: bold;
  margin-left: 0em;
}
ul.toc li li {
  line-height: normal;
  font-weight: normal;
  font-size: 11pt;
  margin-left: 0em;
}
li.excluded {
  font-size: 0pt;
}
ul p {
  margin-left: 0em;
}
.filename, h1, h2, h3, h4 {
  font-family: candara, calibri, segoe, optima, arial, sans-serif;
}
ul.ind, ul.ind ul {
  list-style: none;
  margin-left: 1.5em;
  padding-left: 0em;
  page-break-before: avoid;
}
ul.ind li {
  font-weight: bold;
  line-height: 200%;
  margin-left: 0em;
}
ul.ind li li {
  font-weight: normal;
  line-height: 150%;
  margin-left: 0em;
}
.avoidbreakinside {
  page-break-inside: avoid;
}
.avoidbreakafter {
  page-break-after: avoid;
}
.bcp14 {
  font-style: normal;
  text-transform: lowercase;
  font-variant: small-caps;
}
.comment {
  background-color: yellow;
}
.center {
  text-align: center;
}
.error {
  color: red;
  font-style: italic;
  font-weight: bold;
}
.figure {
  font-weight: bold;
  text-align: center;
  font-size: 10pt;
}
.filename {
  color: #333333;
  font-size: 112%;
  font-weight: bold;
  line-height: 21pt;
  text-align: center;
  margin-top: 0pt;
}
.fn {
  font-weight: bold;
}
.left {
  text-align: left;
}
.right {
  text-align: right;
}
.warning {
  font-size: 130%;
  background-color: yellow;
}
.self {
    color: #999999;
    margin-left: .3em;
    text-decoration: none;
    visibility: hidden;
    -webkit-user-select: none; 
    -moz-user-select: none;
    -ms-user-select: none;
}
.self:hover {
    text-decoration: none;
}
p:hover .self {
    visibility: visible;
}
.docstatus {
  border: 1px solid black;
  display: none;
  float: right;
  margin: 2em;
  padding: 1em;
}

@media screen {
  pre.text, pre.text2 {
    width: 69em;
  }
}

@media print {
  .noprint {
    display: none;
  }

  a {
    color: black;
    text-decoration: none;
  }

  table.header {
    width: 90%;
  }

  td.header {
    width: 50%;
    color: black;
    background-color: white;
    vertical-align: top;
    font-size: 110%;
  }

  ul.toc a:last-child::after {
    content: leader('.') target-counter(attr(href), page);
  }

  ul.ind li li a {
    content: target-counter(attr(href), page);
  }

  pre {
    font-size: 10pt;
  }

  .print2col {
    column-count: 2;
    -moz-column-count: 2;
    column-fill: auto;
  }
}
@page {
  @top-left {
       content: "RFC 3253";
  }
  @top-right {
       content: "March 2002";
  }
  @top-center {
       content: "Versioning Extensions to WebDAV";
  }
  @bottom-left {
       content: "Clemm, et al.";
  }
  @bottom-center {
       content: "Standards Track";
  }
  @bottom-right {
       content: "[Page " counter(page) "]";
  }
}
@page:first {
    @top-left {
      content: normal;
    }
    @top-right {
      content: normal;
    }
    @top-center {
      content: normal;
    }
}
</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Copyright" href="#rfc.copyright"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Basic Versioning Features" href="#rfc.section.2"><link rel="Chapter" title="3 Version-Control Feature" href="#rfc.section.3"><link rel="Chapter" title="4 CHECKOUT-IN-PLACE FEATURE" href="#rfc.section.4"><link rel="Chapter" title="5 Version-History Feature" href="#rfc.section.5"><link rel="Chapter" title="6 Workspace Feature" href="#rfc.section.6"><link rel="Chapter" title="7 UPDATE Feature" href="#rfc.section.7"><link rel="Chapter" title="8 Label Feature" href="#rfc.section.8"><link rel="Chapter" title="9 Working-Resource Feature" href="#rfc.section.9"><link rel="Chapter" title="10 Advanced Versioning Features" href="#rfc.section.10"><link rel="Chapter" title="11 Merge Feature" href="#rfc.section.11"><link rel="Chapter" title="12 Baseline Feature" href="#rfc.section.12"><link rel="Chapter" title="13 Activity Feature" href="#rfc.section.13"><link rel="Chapter" title="14 Version-Controlled-Collection Feature" href="#rfc.section.14"><link rel="Chapter" title="15 Internationalization Considerations" href="#rfc.section.15"><link rel="Chapter" title="16 Security Considerations" href="#rfc.section.16"><link rel="Chapter" title="17 IANA Considerations" href="#rfc.section.17"><link rel="Chapter" title="18 Intellectual Property" href="#rfc.section.18"><link rel="Chapter" title="19 Acknowledgements" href="#rfc.section.19"><link rel="Chapter" href="#rfc.section.20" title="20 References"><link rel="Appendix" title="A Resource Classification" href="#rfc.section.A"><link rel="Alternate" title="Authoritative ASCII Version" href="http://www.ietf.org/rfc/rfc3253.txt"><link rel="Help" title="RFC-Editor's Status Page" href="http://www.rfc-editor.org/info/rfc3253"><link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc3253"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.840, 2016/11/16 05:32:10, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><link rel="schema.dcterms" href="http://purl.org/dc/terms/"><meta name="dcterms.creator" content="Clemm, G."><meta name="dcterms.creator" content="Amsden, J."><meta name="dcterms.creator" content="Ellison, T."><meta name="dcterms.creator" content="Kaler, C."><meta name="dcterms.creator" content="Whitehead, J."><meta name="dcterms.identifier" content="urn:ietf:rfc:3253"><meta name="dcterms.issued" content="2002-03"><meta name="dcterms.abstract" content="This document specifies a set of methods, headers, and resource types that define the WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the complexity of clients that are capable of interoperating with a variety of versioning repository managers, to facilitate widespread deployment of applications capable of utilizing the WebDAV Versioning services. WebDAV versioning includes automatic versioning for versioning-unaware clients, version history management, workspace management, baseline management, activity management, and URL namespace versioning."><meta name="dcterms.isPartOf" content="urn:issn:2070-1721"><meta name="description" content="This document specifies a set of methods, headers, and resource types that define the WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the complexity of clients that are capable of interoperating with a variety of versioning repository managers, to facilitate widespread deployment of applications capable of utilizing the WebDAV Versioning services. WebDAV versioning includes automatic versioning for versioning-unaware clients, version history management, workspace management, baseline management, activity management, and URL namespace versioning."></head><body onload='getMeta(3253,"rfc.meta");'><header><table class="header" id="rfc.headerblock"><tbody><tr><td class="left">Network Working Group</td><td class="right">G. Clemm</td></tr><tr><td class="left">Request for Comments: 3253</td><td class="right">Rational Software</td></tr><tr><td class="left">Category: Standards Track</td><td class="right">J. Amsden</td></tr><tr><td class="left"></td><td class="right">T. Ellison</td></tr><tr><td class="left"></td><td class="right">IBM</td></tr><tr><td class="left"></td><td class="right">C. Kaler</td></tr><tr><td class="left"></td><td class="right">Microsoft</td></tr><tr><td class="left"></td><td class="right">J. Whitehead</td></tr><tr><td class="left"></td><td class="right">U.C. Santa Cruz</td></tr><tr><td class="left"></td><td class="right">March 2002</td></tr></tbody></table><div id="rfc.title"><h1>Versioning Extensions to WebDAV (Web&nbsp;Distributed&nbsp;Authoring&nbsp;and&nbsp;Versioning)</h1></div></header><div id="rfc.meta" class="docstatus" style="display: block;"><b>PROPOSED STANDARD</b><br><i>This document has <a href="http://www.rfc-editor.org/errata_search.php?rfc=3253">errata</a>.</i></div><section id="rfc.status"><h2><a href="#rfc.status">Status of this Memo</a></h2><p>This
 document specifies an Internet standards track protocol for the 
Internet community, and requests discussion and suggestions for 
improvements. Please refer to the current edition of the “Internet 
Official Protocol Standards” (STD 1) for the standardization state and 
status of this protocol. Distribution of this memo is unlimited.</p></section><section id="rfc.copyrightnotice"><h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2><p>Copyright © The Internet Society (2002). All Rights Reserved.</p></section><section id="rfc.abstract"><h2><a href="#rfc.abstract">Abstract</a></h2><p>This
 document specifies a set of methods, headers, and resource types that 
define the WebDAV (Web Distributed Authoring and Versioning) versioning 
extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the
 complexity of clients that are capable of interoperating with a variety
 of versioning repository managers, to facilitate widespread deployment 
of applications capable of utilizing the WebDAV Versioning services. 
WebDAV versioning includes automatic versioning for versioning-unaware 
clients, version history management, workspace management, baseline 
management, activity management, and URL namespace versioning.</p></section><hr class="noprint"><nav id="rfc.toc"><h2 class="np"><a href="#rfc.toc">Table of Contents</a></h2><ul class="toc"><li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction</a><ul><li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.1">Relationship to WebDAV</a></li><li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.2">Notational Conventions</a></li><li><a href="#rfc.section.1.3">1.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.3">Terms</a></li><li><a href="#rfc.section.1.4">1.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.4">Property Values</a><ul><li><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.4.1">Initial Property Value</a></li><li><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#protected.property.value">Protected Property Value</a></li><li><a href="#rfc.section.1.4.3">1.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#computed.property.value">Computed Property Value</a></li><li><a href="#rfc.section.1.4.4">1.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.4.4">Boolean Property Value</a></li><li><a href="#rfc.section.1.4.5">1.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.4.5">DAV:href Property Value</a></li></ul></li><li><a href="#rfc.section.1.5">1.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.5">DAV Namespace XML Elements in Request and Response Bodies</a></li><li><a href="#rfc.section.1.6">1.6</a>&nbsp;&nbsp;&nbsp;<a href="#method.preconditions.and.postconditions">Method Preconditions and Postconditions</a><ul><li><a href="#rfc.section.1.6.1">1.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.6.1">Example - CHECKOUT request with DAV:must-be-checked-in response</a></li></ul></li><li><a href="#rfc.section.1.7">1.7</a>&nbsp;&nbsp;&nbsp;<a href="#clarification.of.copy.semantics.with.overwrite-t">Clarification of COPY Semantics with Overwrite:T</a></li><li><a href="#rfc.section.1.8">1.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.8">Versioning Methods and Write Locks</a></li></ul></li><li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Basic Versioning Features</a><ul><li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1">Basic Versioning Packages</a></li><li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#basic.versioning.semantics">Basic Versioning Semantics</a><ul><li><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#creating.a.version-controlled.resource">Creating a Version-Controlled Resource</a></li><li><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.2.2">Modifying a Version-Controlled Resource</a></li><li><a href="#rfc.section.2.2.3">2.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.2.3">Reporting</a></li></ul></li></ul></li><li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Version-Control Feature</a><ul><li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Additional Resource Properties</a><ul><li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_comment">DAV:comment</a></li><li><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_creator-displayname">DAV:creator-displayname</a></li><li><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_supported-method-set">DAV:supported-method-set (protected)</a></li><li><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_supported-live-property-set">DAV:supported-live-property-set (protected)</a></li><li><a href="#rfc.section.3.1.5">3.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_supported-report-set">DAV:supported-report-set (protected)</a></li></ul></li><li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2">Version-Controlled Resource Properties</a><ul><li><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_checked-in">DAV:checked-in (protected)</a></li><li><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_auto-version">DAV:auto-version</a></li></ul></li><li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3">Checked-Out Resource Properties</a><ul><li><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_checked-out">DAV:checked-out (protected)</a></li><li><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_predecessor-set">DAV:predecessor-set</a></li></ul></li><li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.4">Version Properties</a><ul><li><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.4.1">DAV:predecessor-set (protected)</a></li><li><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_successor-set">DAV:successor-set (computed)</a></li><li><a href="#rfc.section.3.4.3">3.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_checkout-set">DAV:checkout-set (computed)</a></li><li><a href="#rfc.section.3.4.4">3.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_version-name">DAV:version-name (protected)</a></li></ul></li><li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_VERSION-CONTROL">VERSION-CONTROL Method</a><ul><li><a href="#rfc.section.3.5.1">3.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.5.1">Example - VERSION-CONTROL</a></li></ul></li><li><a href="#rfc.section.3.6">3.6</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_REPORT">REPORT Method</a></li><li><a href="#rfc.section.3.7">3.7</a>&nbsp;&nbsp;&nbsp;<a href="#REPORT_version-tree">DAV:version-tree Report</a><ul><li><a href="#rfc.section.3.7.1">3.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.7.1">Example - DAV:version-tree Report</a></li></ul></li><li><a href="#rfc.section.3.8">3.8</a>&nbsp;&nbsp;&nbsp;<a href="#REPORT_expand-property">DAV:expand-property Report</a><ul><li><a href="#rfc.section.3.8.1">3.8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.8.1">Example - DAV:expand-property</a></li></ul></li><li><a href="#rfc.section.3.9">3.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.9">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.3.10">3.10</a>&nbsp;&nbsp;&nbsp;<a href="#additional.put.semantics">Additional PUT Semantics</a></li><li><a href="#rfc.section.3.11">3.11</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.11">Additional PROPFIND Semantics</a></li><li><a href="#rfc.section.3.12">3.12</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.12">Additional PROPPATCH Semantics</a></li><li><a href="#rfc.section.3.13">3.13</a>&nbsp;&nbsp;&nbsp;<a href="#additional.delete.semantics">Additional DELETE Semantics</a></li><li><a href="#rfc.section.3.14">3.14</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.14">Additional COPY Semantics</a></li><li><a href="#rfc.section.3.15">3.15</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.15">Additional MOVE Semantics</a></li><li><a href="#rfc.section.3.16">3.16</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.16">Additional UNLOCK Semantics</a></li></ul></li><li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#checkout-in-place.feature">CHECKOUT-IN-PLACE FEATURE</a><ul><li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Additional Version Properties</a><ul><li><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_checkout-fork">DAV:checkout-fork</a></li><li><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_checkin-fork">DAV:checkin-fork</a></li></ul></li><li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.2">Checked-Out Resource Properties</a><ul><li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.2.1">DAV:checkout-fork</a></li><li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.2.2">DAV:checkin-fork</a></li></ul></li><li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#checkout.method.applied.to.a.version-controlled.resource">CHECKOUT Method (applied to a version-controlled resource)</a><ul><li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.3.1">Example - CHECKOUT of a version-controlled resource</a></li></ul></li><li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#checkin.method.applied.to.a.version-controlled.resource">CHECKIN Method (applied to a version-controlled resource)</a><ul><li><a href="#rfc.section.4.4.1">4.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.4.1">Example - CHECKIN</a></li></ul></li><li><a href="#rfc.section.4.5">4.5</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_UNCHECKOUT">UNCHECKOUT Method</a><ul><li><a href="#rfc.section.4.5.1">4.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.5.1">Example - UNCHECKOUT</a></li></ul></li><li><a href="#rfc.section.4.6">4.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.6">Additional OPTIONS Semantics</a></li></ul></li><li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#version-history.feature">Version-History Feature</a><ul><li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.1">Version History Properties</a><ul><li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_version-set">DAV:version-set (protected)</a></li><li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_root-version">DAV:root-version (computed)</a></li></ul></li><li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.2">Additional Version-Controlled Resource Properties</a><ul><li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_version-history">DAV:version-history (computed)</a></li></ul></li><li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.3">Additional Version Properties</a><ul><li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.3.1">DAV:version-history (computed)</a></li></ul></li><li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#REPORT_locate-by-history">DAV:locate-by-history Report</a><ul><li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.4.1">Example - DAV:locate-by-history Report</a></li></ul></li><li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.5">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.5.6">5.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.6">Additional DELETE Semantics</a></li><li><a href="#rfc.section.5.7">5.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.7">Additional COPY Semantics</a></li><li><a href="#rfc.section.5.8">5.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.8">Additional MOVE Semantics</a></li><li><a href="#rfc.section.5.9">5.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.9">Additional VERSION-CONTROL Semantics</a></li><li><a href="#rfc.section.5.10">5.10</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.10">Additional CHECKIN Semantics</a></li></ul></li><li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#workspace.feature">Workspace Feature</a><ul><li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.1">Workspace Properties</a><ul><li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_workspace-checkout-set">DAV:workspace-checkout-set (computed)</a></li></ul></li><li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.2">Additional Resource Properties</a><ul><li><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_workspace">DAV:workspace (protected)</a></li></ul></li><li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_MKWORKSPACE">MKWORKSPACE Method</a><ul><li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.3.1">Example - MKWORKSPACE</a></li></ul></li><li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#additional.options.semantics.with.workspace.feature">Additional OPTIONS Semantics</a><ul><li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.4.1">Example - OPTIONS</a></li></ul></li><li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.5">Additional DELETE Semantics</a></li><li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.6">Additional MOVE Semantics</a></li><li><a href="#rfc.section.6.7">6.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.7">Additional VERSION-CONTROL Semantics</a><ul><li><a href="#rfc.section.6.7.1">6.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.7.1">Example - VERSION-CONTROL (using an existing version history)</a></li></ul></li></ul></li><li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7">UPDATE Feature</a><ul><li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_UPDATE">UPDATE Method</a><ul><li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7.1.1">Example - UPDATE</a></li></ul></li><li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7.2">Additional OPTIONS Semantics</a></li></ul></li><li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#label.feature">Label Feature</a><ul><li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.1">Additional Version Properties</a><ul><li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_label-name-set">DAV:label-name-set (protected)</a></li></ul></li><li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_LABEL">LABEL Method</a><ul><li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.2.1">Example - Setting a label</a></li></ul></li><li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#label.header">Label Header</a></li><li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.4">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.8.5">8.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.5">Additional GET Semantics</a></li><li><a href="#rfc.section.8.6">8.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.6">Additional PROPFIND Semantics</a></li><li><a href="#rfc.section.8.7">8.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.7">Additional COPY Semantics</a></li><li><a href="#rfc.section.8.8">8.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.8">Additional CHECKOUT Semantics</a></li><li><a href="#rfc.section.8.9">8.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.9">Additional UPDATE Semantics</a></li></ul></li><li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9">Working-Resource Feature</a><ul><li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1">Additional Version Properties</a><ul><li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.1">DAV:checkout-fork</a></li><li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.2">DAV:checkin-fork</a></li></ul></li><li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.2">Working Resource Properties</a><ul><li><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_auto-update">DAV:auto-update (protected)</a></li><li><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.2.2">DAV:checkout-fork</a></li><li><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.2.3">DAV:checkin-fork</a></li></ul></li><li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.3">CHECKOUT Method (applied to a version)</a><ul><li><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.3.1">Example - CHECKOUT of a version</a></li></ul></li><li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.4">CHECKIN Method (applied to a working resource)</a><ul><li><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.4.1">Example - CHECKIN of a working resource</a></li></ul></li><li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.5">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.6">Additional COPY Semantics</a></li><li><a href="#rfc.section.9.7">9.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.7">Additional MOVE Semantics</a></li></ul></li><li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#advanced.versioning.features">Advanced Versioning Features</a><ul><li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.10.1">Advanced Versioning Packages</a></li><li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.10.2">Advanced Versioning Terms</a></li></ul></li><li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#merge.feature">Merge Feature</a><ul><li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.1">Additional Checked-Out Resource Properties</a><ul><li><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_merge-set">DAV:merge-set</a></li><li><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_auto-merge-set">DAV:auto-merge-set</a></li></ul></li><li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_MERGE">MERGE Method</a><ul><li><a href="#rfc.section.11.2.1">11.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.2.1">Example - MERGE</a></li></ul></li><li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.3">DAV:merge-preview Report</a><ul><li><a href="#rfc.section.11.3.1">11.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.3.1">Example - DAV:merge-preview Report</a></li></ul></li><li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.4">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.11.5">11.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.5">Additional DELETE Semantics</a></li><li><a href="#rfc.section.11.6">11.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.6">Additional CHECKIN Semantics</a></li></ul></li><li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#baseline.feature">Baseline Feature</a><ul><li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.1">Version-Controlled Configuration Properties</a><ul><li><a href="#rfc.section.12.1.1">12.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_baseline-controlled-collection">DAV:baseline-controlled-collection (protected)</a></li></ul></li><li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.2">Checked-Out Configuration Properties</a><ul><li><a href="#rfc.section.12.2.1">12.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_subbaseline-set">DAV:subbaseline-set</a></li></ul></li><li><a href="#rfc.section.12.3">12.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.3">Baseline Properties</a><ul><li><a href="#rfc.section.12.3.1">12.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_baseline-collection">DAV:baseline-collection (protected)</a></li><li><a href="#rfc.section.12.3.2">12.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.3.2">DAV:subbaseline-set (protected)</a></li></ul></li><li><a href="#rfc.section.12.4">12.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.4">Additional Resource Properties</a><ul><li><a href="#rfc.section.12.4.1">12.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_version-controlled-configuration">DAV:version-controlled-configuration (computed)</a></li></ul></li><li><a href="#rfc.section.12.5">12.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.5">Additional Workspace Properties</a><ul><li><a href="#rfc.section.12.5.1">12.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_baseline-controlled-collection-set">DAV:baseline-controlled-collection-set (computed)</a></li></ul></li><li><a href="#rfc.section.12.6">12.6</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_BASELINE-CONTROL">BASELINE-CONTROL Method</a><ul><li><a href="#rfc.section.12.6.1">12.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.6.1">Example - BASELINE-CONTROL</a></li></ul></li><li><a href="#rfc.section.12.7">12.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.7">DAV:compare-baseline Report</a><ul><li><a href="#rfc.section.12.7.1">12.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.7.1">Example - DAV:compare-baseline Report</a></li></ul></li><li><a href="#rfc.section.12.8">12.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.8">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.12.9">12.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.9">Additional MKCOL Semantics</a></li><li><a href="#rfc.section.12.10">12.10</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.10">Additional COPY Semantics</a></li><li><a href="#rfc.section.12.11">12.11</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.11">Additional CHECKOUT Semantics</a></li><li><a href="#rfc.section.12.12">12.12</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.12">Additional CHECKIN Semantics</a></li><li><a href="#rfc.section.12.13">12.13</a>&nbsp;&nbsp;&nbsp;<a href="#additional.update.semantics.with.baseline.feature">Additional UPDATE Semantics</a></li><li><a href="#rfc.section.12.14">12.14</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.14">Additional MERGE Semantics</a></li></ul></li><li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#activity.feature">Activity Feature</a><ul><li><a href="#rfc.section.13.1">13.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.1">Activity Properties</a><ul><li><a href="#rfc.section.13.1.1">13.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_activity-version-set">DAV:activity-version-set (computed)</a></li><li><a href="#rfc.section.13.1.2">13.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_activity-checkout-set">DAV:activity-checkout-set (computed)</a></li><li><a href="#rfc.section.13.1.3">13.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_subactivity-set">DAV:subactivity-set</a></li><li><a href="#rfc.section.13.1.4">13.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_current-workspace-set">DAV:current-workspace-set (computed)</a></li></ul></li><li><a href="#rfc.section.13.2">13.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.2">Additional Version Properties</a><ul><li><a href="#rfc.section.13.2.1">13.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_activity-set">DAV:activity-set</a></li></ul></li><li><a href="#rfc.section.13.3">13.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.3">Additional Checked-Out Resource Properties</a><ul><li><a href="#rfc.section.13.3.1">13.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_unreserved">DAV:unreserved</a></li><li><a href="#rfc.section.13.3.2">13.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.3.2">DAV:activity-set</a></li></ul></li><li><a href="#rfc.section.13.4">13.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.4">Additional Workspace Properties</a><ul><li><a href="#rfc.section.13.4.1">13.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_current-activity-set">DAV:current-activity-set</a></li></ul></li><li><a href="#rfc.section.13.5">13.5</a>&nbsp;&nbsp;&nbsp;<a href="#METHOD_MKACTIVITY">MKACTIVITY Method</a><ul><li><a href="#rfc.section.13.5.1">13.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.5.1">Example - MKACTIVITY</a></li></ul></li><li><a href="#rfc.section.13.6">13.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.6">DAV:latest-activity-version Report</a></li><li><a href="#rfc.section.13.7">13.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.7">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.13.8">13.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.8">Additional DELETE Semantics</a></li><li><a href="#rfc.section.13.9">13.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.9">Additional MOVE Semantics</a></li><li><a href="#rfc.section.13.10">13.10</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.10">Additional CHECKOUT Semantics</a><ul><li><a href="#rfc.section.13.10.1">13.10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.10.1">Example - CHECKOUT with an activity</a></li></ul></li><li><a href="#rfc.section.13.11">13.11</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.11">Additional CHECKIN Semantics</a></li><li><a href="#rfc.section.13.12">13.12</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.12">Additional MERGE Semantics</a></li></ul></li><li><a href="#rfc.section.14">14.</a>&nbsp;&nbsp;&nbsp;<a href="#version-controlled-collection.feature">Version-Controlled-Collection Feature</a><ul><li><a href="#rfc.section.14.1">14.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.1">Version-Controlled Collection Properties</a><ul><li><a href="#rfc.section.14.1.1">14.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_eclipsed-set">DAV:eclipsed-set (computed)</a></li></ul></li><li><a href="#rfc.section.14.2">14.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.2">Collection Version Properties</a><ul><li><a href="#rfc.section.14.2.1">14.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#PROPERTY_version-controlled-binding-set">DAV:version-controlled-binding-set (protected)</a></li></ul></li><li><a href="#rfc.section.14.3">14.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.3">Additional OPTIONS Semantics</a></li><li><a href="#rfc.section.14.4">14.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.4">Additional DELETE Semantics</a></li><li><a href="#rfc.section.14.5">14.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.5">Additional MKCOL Semantics</a></li><li><a href="#rfc.section.14.6">14.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.6">Additional COPY Semantics</a></li><li><a href="#rfc.section.14.7">14.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.7">Additional MOVE Semantics</a></li><li><a href="#rfc.section.14.8">14.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.8">Additional VERSION-CONTROL Semantics</a></li><li><a href="#rfc.section.14.9">14.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.9">Additional CHECKOUT Semantics</a></li><li><a href="#rfc.section.14.10">14.10</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.10">Additional CHECKIN Semantics</a></li><li><a href="#rfc.section.14.11">14.11</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.14.11">Additional UPDATE and MERGE Semantics</a></li></ul></li><li><a href="#rfc.section.15">15.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.15">Internationalization Considerations</a></li><li><a href="#rfc.section.16">16.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.16">Security Considerations</a><ul><li><a href="#rfc.section.16.1">16.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.16.1">Auditing and Traceability</a></li><li><a href="#rfc.section.16.2">16.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.16.2">Increased Need for Access Control</a></li><li><a href="#rfc.section.16.3">16.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.16.3">Security Through Obscurity</a></li><li><a href="#rfc.section.16.4">16.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.16.4">Denial of Service</a></li></ul></li><li><a href="#rfc.section.17">17.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.17">IANA Considerations</a></li><li><a href="#rfc.section.18">18.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.18">Intellectual Property</a></li><li><a href="#rfc.section.19">19.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.19">Acknowledgements</a></li><li><a href="#rfc.section.20">20.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li><li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A">Resource Classification</a><ul><li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.1">DeltaV-Compliant Unmapped URL (a URL that identifies no resource)</a></li><li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.2">DeltaV-Compliant Resource</a></li><li><a href="#rfc.section.A.3">A.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.3">DeltaV-Compliant Collection</a></li><li><a href="#rfc.section.A.4">A.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.4">Versionable Resource</a></li><li><a href="#rfc.section.A.5">A.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.5">Version-Controlled Resource</a></li><li><a href="#rfc.section.A.6">A.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.6">Version</a></li><li><a href="#rfc.section.A.7">A.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.7">Checked-In Version-Controlled Resource</a></li><li><a href="#rfc.section.A.8">A.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.8">Checked-Out Resource</a></li><li><a href="#rfc.section.A.9">A.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.9">Checked-Out Version-Controlled Resource (checkout-in-place)</a></li><li><a href="#rfc.section.A.10">A.10</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.10">Working Resource (working-resource)</a></li><li><a href="#rfc.section.A.11">A.11</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.11">Version History (version-history)</a></li><li><a href="#rfc.section.A.12">A.12</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.12">Workspace (workspace)</a></li><li><a href="#rfc.section.A.13">A.13</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.13">Activity (activity)</a></li><li><a href="#rfc.section.A.14">A.14</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.14">Version-Controlled Collection (version-controlled-collection)</a></li><li><a href="#rfc.section.A.15">A.15</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.15">Collection Version (version-controlled-collection)</a></li><li><a href="#rfc.section.A.16">A.16</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.16">Version-Controlled Configuration (baseline)</a></li><li><a href="#rfc.section.A.17">A.17</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.17">Baseline (baseline)</a></li><li><a href="#rfc.section.A.18">A.18</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A.18">Checked-Out Version-Controlled Configuration (baseline)</a></li></ul></li><li><a href="#rfc.index">Index</a></li><li><a href="#rfc.authors">Authors' Addresses</a></li><li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li></ul></nav><hr class="noprint"><section id="n-introduction"><h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#n-introduction">Introduction</a></h2><div id="rfc.section.1.p.1" class="avoidbreakafter"><p>This
 document specifies a set of methods, headers, and properties that 
define the WebDAV (Web Distributed Authoring and Versioning) versioning 
extensions to the HTTP/1.1 protocol. Versioning is concerned with 
tracking and accessing the history of important states of a web 
resource, such as a standalone web page. The benefits of versioning in 
the context of the worldwide web include:<a class="self" href="#rfc.section.1.p.1">¶</a></p></div><div id="rfc.section.1.p.2"><ul><li>A
 resource has an explicit history and a persistent identity across the 
various states it has had during the course of that history. It allows 
browsing through past and alternative versions of a resource. Frequently
 the modification and authorship history of a resource is critical 
information in itself.</li><li>Resource states (versions) are given 
stable names that can support externally stored links for annotation and
 link server support. Both annotation and link servers frequently need 
to store stable references to portions of resources that are not under 
their direct control. By providing stable states of resources, version 
control systems allow not only stable pointers into those resources, but
 also well defined methods to determine the relationships of those 
states of a resource.</li></ul></div><div id="rfc.section.1.p.3"><p>WebDAV Versioning defines both basic and advanced versioning functionality.<a class="self" href="#rfc.section.1.p.3">¶</a></p></div><div id="rfc.section.1.p.4"><p>Basic versioning allows users to: <a class="self" href="#rfc.section.1.p.4">¶</a></p><ul><li>Put a resource under version control</li><li>Determine whether a resource is under version control</li><li>Determine whether a resource update will automatically be captured as a new version</li><li>Create and access distinct versions of a resource</li></ul></div><div id="rfc.section.1.p.5"><p>Advanced
 versioning provides additional functionality for parallel development 
and configuration management of sets of web resources.<a class="self" href="#rfc.section.1.p.5">¶</a></p></div><div id="rfc.section.1.p.6"><p>This
 document will first define the properties and method semantics for the 
basic versioning features, and then define the additional properties and
 method semantics for the advanced versioning features. An implementer 
that is only interested in basic versioning should skip the advanced 
versioning sections (<a href="#advanced.versioning.features" title="Advanced Versioning Features">Section&nbsp;10</a> to <a href="#version-controlled-collection.feature" title="Version-Controlled-Collection Feature">Section&nbsp;14</a>).<a class="self" href="#rfc.section.1.p.6">¶</a></p></div><section id="n-relationship-to-webdav"><h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#n-relationship-to-webdav">Relationship to WebDAV</a></h3><div id="rfc.section.1.1.p.1"><p>To
 maximize interoperability and the use of existing protocol 
functionality, versioning support is designed as extensions to the 
WebDAV protocol <a href="#RFC2518" id="rfc.xref.RFC2518.1"><cite title="HTTP Extensions for Distributed Authoring -- WEBDAV">[RFC2518]</cite></a>, which itself is an extension to the HTTP protocol <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
 All method marshalling and postconditions defined by RFC 2518 and RFC 
2616 continue to hold, to ensure that versioning unaware clients can 
interoperate successfully with versioning servers. Although the 
versioning extensions are designed to be orthogonal to most aspects of 
the WebDAV and HTTP protocols, a clarification to RFC 2518 is required 
for effective interoperable versioning. This clarification is described 
in <a href="#clarification.of.copy.semantics.with.overwrite-t" title="Clarification of COPY Semantics with Overwrite:T">Section&nbsp;1.7</a>.<a class="self" href="#rfc.section.1.1.p.1">¶</a></p></div></section><section id="n-notational-conventions"><h3 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#n-notational-conventions">Notational Conventions</a></h3><div id="rfc.section.1.2.p.1"><p>The
 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in <cite title="Key words for use in RFCs to Indicate Requirement Levels" id="rfc.xref.RFC2119.1">RFC 2119</cite>.<a class="self" href="#rfc.section.1.2.p.1">¶</a></p></div><div id="rfc.section.1.2.p.2"><p>The term "protected" is placed in parentheses following the definition of a protected property (see <a href="#protected.property.value" title="Protected Property Value">Section&nbsp;1.4.2</a>).<a class="self" href="#rfc.section.1.2.p.2">¶</a></p></div><div id="rfc.section.1.2.p.3"><p>The term "computed" is placed in parentheses following the definition of a computed property (see <a href="#computed.property.value" title="Computed Property Value">Section&nbsp;1.4.3</a>).<a class="self" href="#rfc.section.1.2.p.3">¶</a></p></div><div id="rfc.section.1.2.p.4"><p>When
 an XML element type in the "DAV:" namespace is referenced in this 
document outside of the context of an XML fragment, the string "DAV:" 
will be prefixed to the element type.<a class="self" href="#rfc.section.1.2.p.4">¶</a></p></div><div id="rfc.section.1.2.p.5"><p>When
 a method is defined in this document, a list of preconditions and 
postconditions will be defined for that method. If the semantics of an 
existing method is being extended, a list of additional preconditions 
and postconditions will be defined. A precondition or postcondition is 
prefixed by a parenthesized XML element type that identifies that 
precondition or postcondition (see <a href="#method.preconditions.and.postconditions" title="Method Preconditions and Postconditions">Section&nbsp;1.6</a>).<a class="self" href="#rfc.section.1.2.p.5">¶</a></p></div></section><section id="n-terms"><h3 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#n-terms">Terms</a></h3><div id="rfc.section.1.3.p.1"><p>This document uses the terms defined in RFC 2616, in RFC 2518, and in this section. <a href="#basic.versioning.semantics" title="Basic Versioning Semantics">Section&nbsp;2.2</a> defines the semantic versioning model underlying this terminology.<a class="self" href="#rfc.section.1.3.p.1">¶</a></p></div><div id="rfc.section.1.3.p.2"><p><dfn>Version Control</dfn><span id="rfc.iref.v.1"></span>, <dfn>Checked-In</dfn><span id="rfc.iref.c.1"></span>, <dfn>Checked-Out</dfn><span id="rfc.iref.c.2"></span> <a class="self" href="#rfc.section.1.3.p.2">¶</a></p><ul class="empty"><li>"Version
 control" is a set of constraints on how a resource can be updated. A 
resource under version control is either in a "checked-in" or 
"checked-out" state, and the version control constraints apply only 
while the resource is in the checked-in state.</li></ul></div><div id="rfc.section.1.3.p.3"><p><dfn>Versionable Resource</dfn><span id="rfc.iref.v.2"></span> <a class="self" href="#rfc.section.1.3.p.3">¶</a></p><ul class="empty"><li>A "versionable resource" is a resource that can be put under version control.</li></ul></div><div id="rfc.section.1.3.p.4"><p><dfn>Version-Controlled Resource</dfn><span id="rfc.iref.v.3"></span> <a class="self" href="#rfc.section.1.3.p.4">¶</a></p><ul class="empty"><li>When
 a versionable resource is put under version control, it becomes a 
"version-controlled resource". A version-controlled resource can be 
"checked out" to allow modification of its content or dead properties by
 standard HTTP and WebDAV methods.</li></ul></div><div id="rfc.section.1.3.p.5"><p><dfn>Checked-Out Resource</dfn><span id="rfc.iref.c.3"></span> <a class="self" href="#rfc.section.1.3.p.5">¶</a></p><ul class="empty"><li>A "checked-out resource" is a resource under version control that is in the checked-out state.</li></ul></div><div id="rfc.section.1.3.p.6"><p><dfn>Version Resource</dfn><span id="rfc.iref.v.4"></span> <a class="self" href="#rfc.section.1.3.p.6">¶</a></p><ul class="empty"><li>A
 "version resource", or simply "version", is a resource that contains a 
copy of a particular state (content and dead properties) of a 
version-controlled resource. A version is created by "checking in" a 
checked-out resource. The server allocates a distinct new URL for each 
new version, and this URL will never be used to identify any resource 
other than that version. The content and dead properties of a version 
never change.</li></ul></div><div id="rfc.section.1.3.p.7"><p><dfn>Version History Resource</dfn><span id="rfc.iref.v.5"></span> <a class="self" href="#rfc.section.1.3.p.7">¶</a></p><ul class="empty"><li>A
 "version history resource", or simply "version history", is a resource 
that contains all the versions of a particular version-controlled 
resource.</li></ul></div><div id="rfc.section.1.3.p.8"><p><dfn>Version Name</dfn><span id="rfc.iref.v.6"></span> <a class="self" href="#rfc.section.1.3.p.8">¶</a></p><ul class="empty"><li>A
 "version name" is a string chosen by the server to distinguish one 
version of a version history from the other versions of that version 
history. Versions from different version histories may have the same 
version name.</li></ul></div><div id="rfc.section.1.3.p.9"><p><dfn>Predecessor</dfn><span id="rfc.iref.p.1"></span>, <dfn>Successor</dfn><span id="rfc.iref.s.1"></span>, <dfn>Ancestor</dfn><span id="rfc.iref.a.1"></span>, <dfn>Descendant</dfn><span id="rfc.iref.d.1"></span> <a class="self" href="#rfc.section.1.3.p.9">¶</a></p><ul class="empty"><li>When
 a version-controlled resource is checked out and then subsequently 
checked in, the version that was checked out becomes a "predecessor" of 
the version created by the checkin. A client can specify multiple 
predecessors for a new version if the new version is logically a merge 
of those predecessors. When a version is connected to another version by
 traversing one or more predecessor relations, it is called an 
"ancestor" of that version. The inverse of the predecessor and ancestor 
relations are the "successor" and "descendant" relations. Therefore, if X
 is a predecessor of Y, then Y is a successor of X, and if X is an 
ancestor of Y, then Y is a descendant of X.</li></ul></div><div id="rfc.section.1.3.p.10"><p><dfn>Root Version Resource</dfn><span id="rfc.iref.r.1"></span> <a class="self" href="#rfc.section.1.3.p.10">¶</a></p><ul class="empty"><li>The
 "root version resource", or simply "root version", is the version in a 
version history that is an ancestor of every other version in that 
version history.</li></ul></div><div id="rfc.section.1.3.p.11"><p><dfn>Workspace Resource</dfn><span id="rfc.iref.w.1"></span> <a class="self" href="#rfc.section.1.3.p.11">¶</a></p><ul class="empty"><li>A
 "workspace resource", or simply "workspace", is a collection that 
contains at most one version-controlled resource for a given version 
history (see <a href="#workspace.feature" title="Workspace Feature">Section&nbsp;6</a>).</li></ul></div><div id="rfc.section.1.3.p.12"><p><dfn>Working Resource</dfn><span id="rfc.iref.w.2"></span> <a class="self" href="#rfc.section.1.3.p.12">¶</a></p><ul class="empty"><li>A
 "working resource" is a checked-out resource created by the server at a
 server-defined URL when a version (instead of a version-controlled 
resource) is checked out. Unlike a checked-out version-controlled 
resource, a working resource is deleted when it is checked in.</li></ul></div><div id="rfc.section.1.3.p.13"><p><dfn>Fork</dfn><span id="rfc.iref.f.1"></span>, <dfn>Merge</dfn><span id="rfc.iref.m.1"></span> <a class="self" href="#rfc.section.1.3.p.13">¶</a></p><ul class="empty"><li>When
 a second successor is added to a version, this creates a "fork" in the 
version history. When a version is created with multiple predecessors, 
this creates a "merge" in the version history. A server may restrict the
 version history to be linear (with no forks or merges), but an 
interoperable versioning client should be prepared to deal with both 
forks and merges in the version history.</li></ul></div><div id="rfc.section.1.3.p.14"><p>The
 following diagram illustrates several of the previous definitions. Each
 box represents a version and each line between two boxes represents a 
predecessor/successor relationship. For example, it shows V3 is a 
predecessor of V5, V7 is a successor of V5, V1 is an ancestor of V4, and
 V7 is a descendant of V4. It also shows that there is a fork at version
 V2 and a merge at version V7.<a class="self" href="#rfc.section.1.3.p.14">¶</a></p></div><div id="rfc.figure.u.1"><p>History of foo.html</p><pre class="drawing">                 

                         ┌───┐
   Root Version -------&gt; │   │ V1
                         └───┘           ^
                           |             |
                           |             |
                         ┌───┐           |
   Version Name ----&gt; V2 │   │           | Ancestor
                         └───┘           |
                         /    \          |
                        /      \         |
                   ┌───┐       ┌───┐
                   │   │ V3    │   │ V4
                ^  └───┘       └───┘
                |    |           |       |
   Predecessor  |    |           |       |
                   ┌───┐       ┌───┐     |
                   │   │ V5    │   │ V6  | Descendant
                   └───┘       └───┘     |
   Successor    |       \      /         |
                |        \    /          |
                v        ┌───┐           v
                         │   │ V7
                         └───┘
</pre></div><div id="rfc.section.1.3.p.15"><p><dfn>Label</dfn><span id="rfc.iref.l.1"></span> <a class="self" href="#rfc.section.1.3.p.15">¶</a></p><ul class="empty"><li>A
 "label" is a name that can be used to select a version from a version 
history. A label can be assigned by either a client or the server. The 
same label can be used in different version histories.</li></ul></div></section><section id="n-property-values"><h3 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a href="#n-property-values">Property Values</a></h3><section id="n-initial-property-value"><h4 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a href="#n-initial-property-value">Initial Property Value</a></h4><div id="rfc.section.1.4.1.p.1"><p>Unless
 an initial value of a property of a given type is defined by this 
document, the initial value of a property of that type is implementation
 dependent.<a class="self" href="#rfc.section.1.4.1.p.1">¶</a></p></div></section><section id="protected.property.value"><h4 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;<a href="#protected.property.value">Protected Property Value</a></h4><div id="rfc.section.1.4.2.p.1"><p>When
 a property of a specific kind of resource is "protected", the property 
value cannot be updated on that kind of resource except by a method 
explicitly defined as updating that specific property. In particular, a 
protected property cannot be updated with a PROPPATCH request. Note that
 a given property can be protected on one kind of resource, but not 
protected on another kind of resource.<a class="self" href="#rfc.section.1.4.2.p.1">¶</a></p></div></section><section id="computed.property.value"><h4 id="rfc.section.1.4.3"><a href="#rfc.section.1.4.3">1.4.3</a>&nbsp;<a href="#computed.property.value">Computed Property Value</a></h4><div id="rfc.section.1.4.3.p.1"><p>When
 a property is "computed", its value is defined in terms of a 
computation based on the content and other properties of that resource, 
or even of some other resource. When the semantics of a method is 
defined in this document, the effect of that method on non-computed 
properties will be specified; the effect of that method on computed 
properties will not be specified, but can be inferred from the 
computation defined for those properties. A computed property is always a
 protected property.<a class="self" href="#rfc.section.1.4.3.p.1">¶</a></p></div></section><section id="n-boolean-property-value"><h4 id="rfc.section.1.4.4"><a href="#rfc.section.1.4.4">1.4.4</a>&nbsp;<a href="#n-boolean-property-value">Boolean Property Value</a></h4><div id="rfc.section.1.4.4.p.1"><p>Some properties take a Boolean value of either "false" or "true".<a class="self" href="#rfc.section.1.4.4.p.1">¶</a></p></div></section><section id="n-dav-href-property-value"><h4 id="rfc.section.1.4.5"><a href="#rfc.section.1.4.5">1.4.5</a>&nbsp;<a href="#n-dav-href-property-value">DAV:href Property Value</a></h4><div id="rfc.section.1.4.5.p.1"><p>The DAV:href XML element is defined in RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.3" id="rfc.xref.RFC2518.2">Section 12.3</a>.<a class="self" href="#rfc.section.1.4.5.p.1">¶</a></p></div></section></section><section id="n-dav-namespace-xml-elements-in-request-and-response-bodies"><h3 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a>&nbsp;<a href="#n-dav-namespace-xml-elements-in-request-and-response-bodies">DAV Namespace XML Elements in Request and Response Bodies</a></h3><div id="rfc.section.1.5.p.1"><p>Although
 WebDAV request and response bodies can be extended by arbitrary XML 
elements, which can be ignored by the message recipient, an XML element 
in the DAV namespace <em class="bcp14">MUST NOT</em> be used in the request or response body of a versioning method unless that XML element is explicitly defined in an IETF RFC.<a class="self" href="#rfc.section.1.5.p.1">¶</a></p></div></section><section id="method.preconditions.and.postconditions"><h3 id="rfc.section.1.6"><a href="#rfc.section.1.6">1.6</a>&nbsp;<a href="#method.preconditions.and.postconditions">Method Preconditions and Postconditions</a></h3><div id="rfc.section.1.6.p.1"><p>A
 "precondition" of a method describes the state of the server that must 
be true for that method to be performed. A "postcondition" of a method 
describes the state of the server that must be true after that method 
has been completed. If a method precondition or postcondition for a 
request is not satisfied, the response status of the request <em class="bcp14">MUST</em>
 be either 403 (Forbidden) if the request should not be repeated because
 it will always fail, or 409 (Conflict) if it is expected that the user 
might be able to resolve the conflict and resubmit the request.<a class="self" href="#rfc.section.1.6.p.1">¶</a></p></div><div id="rfc.section.1.6.p.2"><p>In
 order to allow better client handling of 403 and 409 responses, a 
distinct XML element type is associated with each method precondition 
and postcondition of a request. When a particular precondition is not 
satisfied or a particular postcondition cannot be achieved, the 
appropriate XML element <em class="bcp14">MUST</em> be returned as the 
child of a top-level DAV:error element in the response body, unless 
otherwise negotiated by the request. In a 207 Multi-Status response, the
 DAV:error element would appear in the appropriate 
DAV:responsedescription element.<a class="self" href="#rfc.section.1.6.p.2">¶</a></p></div><section id="n-example---checkout-request-with-dav-must-be-checked-in-response"><h4 id="rfc.section.1.6.1"><a href="#rfc.section.1.6.1">1.6.1</a>&nbsp;<a href="#n-example---checkout-request-with-dav-must-be-checked-in-response">Example - CHECKOUT request with DAV:must-be-checked-in response</a></h4><div id="rfc.figure.u.2"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKOUT /foo.html HTTP/1.1
Host: www.webdav.org
</pre></div><div id="rfc.figure.u.3"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 409 Conflict
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:error xmlns:D="DAV:"&gt;
 &lt;D:must-be-checked-in/&gt;
&lt;/D:error&gt;
</pre></div><div id="rfc.section.1.6.1.p.1"><p>In this example, the request to CHECKOUT /foo.html fails because /foo.html is not checked in.<a class="self" href="#rfc.section.1.6.1.p.1">¶</a></p></div></section></section><section id="clarification.of.copy.semantics.with.overwrite-t"><h3 id="rfc.section.1.7"><a href="#rfc.section.1.7">1.7</a>&nbsp;<a href="#clarification.of.copy.semantics.with.overwrite-t">Clarification of COPY Semantics with Overwrite:T</a></h3><div id="rfc.section.1.7.p.1" class="avoidbreakafter"><p>RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-8.8.4" id="rfc.xref.RFC2518.3">Section 8.8.4</a> states:<a class="self" href="#rfc.section.1.7.p.1">¶</a></p></div><div id="rfc.section.1.7.p.2"><p>"If a resource exists at the destination and the Overwrite header is "T" then prior to performing the copy the server <em class="bcp14">MUST</em> perform a DELETE with "Depth: infinity" on the destination resource."<a class="self" href="#rfc.section.1.7.p.2">¶</a></p></div><div id="rfc.section.1.7.p.3"><p>The
 purpose of this sentence is to ensure that following a COPY, all 
destination resources have the same content and dead properties as the 
corresponding resources identified by the request-URL (where a resource 
with a given name relative to the Destination URL "corresponds" to a 
resource with the same name relative to the request-URL). If at the time
 of the request, there already is a resource at the destination that has
 the same resource type as the corresponding resource at the 
request-URL, that resource <em class="bcp14">MUST NOT</em> be deleted, but <em class="bcp14">MUST</em>
 be updated to have the content and dead properties of its corresponding
 member. If a client wishes all resources at the destination to be 
deleted prior to the COPY, it <em class="bcp14">MUST</em> explicitly issue a DELETE request.<a class="self" href="#rfc.section.1.7.p.3">¶</a></p></div><div id="rfc.section.1.7.p.4"><p>The
 difference between updating a resource and replacing a resource with a 
new resource is especially important when resource history is being 
maintained (the former adds to an existing history, while the latter 
creates a new history). In addition, locking and access control 
constraints might allow you to update a resource, but not allow you to 
delete it and create a new one in its place.<a class="self" href="#rfc.section.1.7.p.4">¶</a></p></div><div id="rfc.section.1.7.p.5"><p>Note that this clarification does not apply to a MOVE request. A MOVE request with Overwrite:T <em class="bcp14">MUST</em> perform the DELETE with "Depth:infinity" on the destination resource prior to performing the MOVE.<a class="self" href="#rfc.section.1.7.p.5">¶</a></p></div></section><section id="n-versioning-methods-and-write-locks"><h3 id="rfc.section.1.8"><a href="#rfc.section.1.8">1.8</a>&nbsp;<a href="#n-versioning-methods-and-write-locks">Versioning Methods and Write Locks</a></h3><div id="rfc.section.1.8.p.1"><p>If a write-locked resource has a non-computed property defined by this document, the property value <em class="bcp14">MUST NOT</em>
 be changed by a request unless the appropriate lock token is included 
in the request. Since every method introduced in this document other 
than REPORT modifies at least one property defined by this document, 
every versioning method other than REPORT is affected by a write lock. 
In particular, the method <em class="bcp14">MUST</em> fail with a 423 
(Locked) status if the resource is write-locked and the appropriate 
token is not specified in an If request header.<a class="self" href="#rfc.section.1.8.p.1">¶</a></p></div></section></section><hr class="noprint"><section id="n-basic-versioning-features"><h2 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#n-basic-versioning-features">Basic Versioning Features</a></h2><div id="rfc.section.2.p.1"><p>Each
 basic versioning feature defines extensions to existing HTTP and WebDAV
 methods, as well as new resource types, live properties, and methods.<a class="self" href="#rfc.section.2.p.1">¶</a></p></div><section id="n-basic-versioning-packages"><h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#n-basic-versioning-packages">Basic Versioning Packages</a></h3><div id="rfc.section.2.1.p.1" class="avoidbreakafter"><p>A server <em class="bcp14">MAY</em>
 support any combination of versioning features. However, in order to 
minimize the complexity of a WebDAV basic versioning client, a WebDAV 
basic versioning server <em class="bcp14">SHOULD</em> support one of the following three "packages" (feature sets):<a class="self" href="#rfc.section.2.1.p.1">¶</a></p></div><div id="rfc.section.2.1.p.2"><ul><li>Core-Versioning Package: version-control</li><li>Basic-Server-Workspace Package: version-control, workspace, version-history, checkout</li><li>Basic-Client-Workspace Package: version-control, working-resource, update, label</li></ul></div><div id="rfc.section.2.1.p.3"><p>The
 core-versioning package supports linear versioning by both 
versioning-aware and versioning-unaware clients. A versioning-aware 
client can use reports and properties to access previous versions of a 
version-controlled resource.<a class="self" href="#rfc.section.2.1.p.3">¶</a></p></div><div id="rfc.section.2.1.p.4"><p>The
 basic workspace packages support parallel development of 
version-controlled resources. Each client has its own configuration of 
the shared version-controlled resources, and can make changes to its 
configuration without disturbing that of another client.<a class="self" href="#rfc.section.2.1.p.4">¶</a></p></div><div id="rfc.section.2.1.p.5"><p>In
 the basic-server-workspace package, all persistent state is maintained 
on the server. Each client has its own workspace resource allocated on 
the server, where each workspace identifies a configuration of the 
shared version-controlled resources. Each client makes changes to its 
workspace, and can transfer changes when appropriate from one workspace 
to another. The server workspace package is appropriate for clients with
 no local persistent state, or for clients that wish to expose their 
working configurations to other clients.<a class="self" href="#rfc.section.2.1.p.5">¶</a></p></div><div id="rfc.section.2.1.p.6"><p>In
 the basic-client-workspace package, each client maintains in local 
persistent storage the state for its configuration of the shared 
version-controlled resources. When a client is ready to make its changes
 visible to other clients, it allocates a set of "working resources" on 
the server, updates the content and dead properties of these working 
resources, and then uses the set of working resources to update the 
version-controlled resources. The working resources are used, instead of
 directly updating the version-controlled resources, so that sets of 
consistent updates can be prepared in parallel by multiple clients. 
Also, a working resource allows a client to prepare a single update that
 requires multiple server requests (e.g. updating both the content and 
dead properties of a resource requires both a PUT and a PROPPATCH). The 
client workspace package simplifies the server implementation by 
requiring each client to maintain its own namespace, but this requires 
that the clients have local persistent state, and does not allow clients
 to expose their working configurations to other clients.<a class="self" href="#rfc.section.2.1.p.6">¶</a></p></div><div id="rfc.section.2.1.p.7"><p>A server that supports both basic workspace packages will interoperate with all basic versioning clients.<a class="self" href="#rfc.section.2.1.p.7">¶</a></p></div></section><section id="basic.versioning.semantics"><h3 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#basic.versioning.semantics">Basic Versioning Semantics</a></h3><section id="creating.a.version-controlled.resource"><h4 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#creating.a.version-controlled.resource">Creating a Version-Controlled Resource</a></h4><div id="rfc.section.2.2.1.p.1" class="avoidbreakafter"><p>In
 order to track the history of the content and dead properties of a 
versionable resource, a user can put the resource under version control 
with a VERSION-CONTROL request. A VERSION-CONTROL request performs three
 distinct operations:<a class="self" href="#rfc.section.2.2.1.p.1">¶</a></p></div><div id="rfc.section.2.2.1.p.2"><ol><li>It
 creates a new "version history resource". In basic versioning, a 
version history resource is not assigned a URL, and hence is not visible
 in the http scheme URL space. However, when the version-history feature
 (see <a href="#version-history.feature" title="Version-History Feature">Section&nbsp;5</a>) is supported, this changes, and each version history resource is assigned a new distinct and unique server-defined URL.</li><li>It
 creates a new "version resource" and adds it to the new version history
 resource. The body and dead properties of the new version resource are a
 copy of those of the versionable resource. The server assigns the new 
version resource a new distinct and unique URL.</li><li>It converts the 
versionable resource into a "version-controlled resource". The 
version-controlled resource continues to be identified by the same URL 
that identified it as a versionable resource. As part of this 
conversion, it adds a DAV:checked-in property, whose value contains the 
URL of the new version resource.</li></ol></div><div id="rfc.section.2.2.1.p.3"><p>Note
 that a versionable resource and a version-controlled resource are not 
new types of resources (i.e. they introduce no new DAV:resourcetype), 
but rather they are any type of resource that supports the methods and 
live properties defined for them in this document, in addition to all 
the methods and live properties implied by their DAV:resourcetype. For 
example, a collection (whose DAV:resourcetype is DAV:collection) is a 
versionable resource if it supports the VERSION-CONTROL method, and is a
 version-controlled resource if it supports the version-controlled 
resource methods and live properties.<a class="self" href="#rfc.section.2.2.1.p.3">¶</a></p></div><div id="rfc.section.2.2.1.p.4"><p>In
 the following example, foo.html is a versionable resource that is put 
under version control. After the VERSION-CONTROL request succeeds, there
 are two additional resources: a new version history resource and a new 
version resource in that version history. The versionable resource is 
converted into a version-controlled resource, whose DAV:checked-in 
property identifies the new version resource. The content and dead 
properties of a resource are represented by the symbol appearing inside 
the box for that resource (e.g., "S1" in the following example).<a class="self" href="#rfc.section.2.2.1.p.4">¶</a></p></div><div id="rfc.figure.u.4"><pre class="drawing">      ===VERSION-CONTROL==&gt;

                |                       ┌────┐ version
                |   version-            │    │ history
   versionable  |   controlled          └────┘ resource
   resource     |   resource              |
   /foo.html    |   /foo.html             |
                |                         v
     ┌────┐     |     ┌────┐ checked-in ┌────┐ version
     │ S1 │     |     │ S1 │-----------&gt;│ S1 │ resource
     └────┘     |     └────┘            └────┘ /his/73/ver/1
</pre></div><div id="rfc.section.2.2.1.p.5"><p>Thus, whereas before the 
VERSION-CONTROL request there was only one, non-version-controlled 
resource, after VERSION-CONTROL there are three separate, distinct 
resources, each containing its own state and properties: the 
version-controlled resource, the version resource, and the version 
history resource. Since the version-controlled resource and the version 
resource are separate, distinct resources, when a method is applied to a
 version-controlled resource, it is only applied to that 
version-controlled resource, and is not applied to the version resource 
that is currently identified by the DAV:checked-in property of that 
version-controlled resource. Although the content and dead properties of
 a checked-in version-controlled resource are required to be the same as
 those of its current DAV:checked-in version, its live properties may 
differ. An implementation may optimize storage by retrieving the content
 and dead properties of a checked-in version-controlled resource from 
its current DAV:checked-in version rather than storing them in the 
version-controlled resource, but this is just an implementation 
optimization.<a class="self" href="#rfc.section.2.2.1.p.5">¶</a></p></div><div id="rfc.section.2.2.1.p.6"><p>Normally, a resource is placed under version control with an explicit VERSION-CONTROL request. A server <em class="bcp14">MAY</em> automatically place every new versionable resource under version control. In this case, the resulting state on the server <em class="bcp14">MUST</em> be the same as if the client had explicitly applied a VERSION-CONTROL request to the versionable resource.<a class="self" href="#rfc.section.2.2.1.p.6">¶</a></p></div></section><section id="n-modifying-a-version-controlled-resource"><h4 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;<a href="#n-modifying-a-version-controlled-resource">Modifying a Version-Controlled Resource</a></h4><div id="rfc.section.2.2.2.p.1"><p>In
 order to use methods like PUT and PROPPATCH to directly modify the 
content or dead properties of a version-controlled resource, the 
version-controlled resource must first be checked out. When the 
checked-out resource is checked in, a new version is created in the 
version history of that version-controlled resource. The version that 
was checked out is remembered as the predecessor of the new version.<a class="self" href="#rfc.section.2.2.2.p.1">¶</a></p></div><div id="rfc.section.2.2.2.p.2" class="avoidbreakafter"><p>The DAV:auto-version property (see <a href="#PROPERTY_auto-version" title="DAV:auto-version">Section&nbsp;3.2.2</a>)
 of a checked-in version-controlled resource determines how it responds 
to a method that attempts to modify its content or dead properties. 
Possible responses include:<a class="self" href="#rfc.section.2.2.2.p.2">¶</a></p></div><div id="rfc.section.2.2.2.p.3"><ul><li>Fail the request. The resource requires an explicit CHECKOUT request for it to be modified (see Sections <a href="#checkout-in-place.feature" title="CHECKOUT-IN-PLACE FEATURE">4</a> and <a href="#PROPERTY_auto-update" title="DAV:auto-update (protected)">9.2.1</a>).</li><li>Automatically
 checkout the resource, perform the modification, and automatically 
checkin the resource. This ensures that every state of the resource is 
tracked by the server, but can result in an excessive number of versions
 being created.</li><li>Automatically checkout the resource, perform the
 modification, and then if the resource is not write-locked, 
automatically checkin the resource. If the resource is write-locked, it 
remains checked-out until the write-lock is removed (either explicitly 
through a subsequent UNLOCK request or implicitly through a time-out of 
the write-lock). This helps a locking client avoid the proliferation of 
versions, while still allowing a non-locking client to update the 
resource.</li><li>Automatically checkout the resource, perform the 
modification, and then leave the resource checked out. If the resource 
is write-locked, it will be automatically checked in when the write-lock
 is removed, but an explicit CHECKIN operation (see <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>)
 is required for a non-write-locked resource. This minimizes the number 
of new versions that will be created by a versioning unaware client, but
 only a versioning aware client can create new versions of a 
non-write-locked resource.</li><li>Fail the request unless the resource 
is write-locked. If it is write-locked, automatically checkout the 
resource and perform the modification. The resource is automatically 
checked in when the write-lock is removed. This minimizes the number of 
new versions that will be created by a versioning unaware client, but 
never automatically checks out a resource that will not subsequently be 
automatically checked in.</li></ul></div><div id="rfc.section.2.2.2.p.4"><p>The
 following diagram illustrates the effect of the checkout/checkin 
process on a version-controlled resource and its version history. The 
symbol inside a box (S1, S2, S3) represents the current content and dead
 properties of the resource represented by that box. The symbol next to a
 box (V1, V2, V3) represents the URL for that resource.<a class="self" href="#rfc.section.2.2.2.p.4">¶</a></p></div><div id="rfc.figure.u.5"><pre class="drawing">        ===checkout==&gt;     ===PUT==&gt;     ===checkin==&gt;


     /foo.html (version-controlled resource)

      ┌────┐    |    ┌────┐    |    ┌────┐    |    ┌────┐
      │ S2 │    |    │ S2 │    |    │ S3 │    |    │ S3 │
      └────┘    |    └────┘    |    └────┘    |    └────┘
   Checked-In=V2|Checked-Out=V2|Checked-Out=V2|Checked-In=V3


     /his/73 (version history for /foo.html)

     ┌────┐     |   ┌────┐     |   ┌────┐     |   ┌────┐
     │ S1 │ V1  |   │ S1 │ V1  |   │ S1 │ V1  |   │ S1 │ V1
     └────┘     |   └────┘     |   └────┘     |   └────┘
        |       |      |       |      |       |      |
        |       |      |       |      |       |      |
     ┌────┐     |   ┌────┐     |   ┌────┐     |   ┌────┐
     │ S2 │ V2  |   │ S2 │ V2  |   │ S2 │ V2  |   │ S2 │ V2
     └────┘     |   └────┘     |   └────┘     |   └────┘
                |              |              |      |
                |              |              |      |
                |              |              |   ┌────┐
                |              |              |   │ S3 │ V3
                |              |              |   └────┘
</pre></div><div id="rfc.section.2.2.2.p.5"><p>Note that a version 
captures only a defined subset of the state of a resource. In 
particular, a version of a basic resource captures its content and dead 
properties, but not its live properties.<a class="self" href="#rfc.section.2.2.2.p.5">¶</a></p></div></section><section id="n-reporting"><h4 id="rfc.section.2.2.3"><a href="#rfc.section.2.2.3">2.2.3</a>&nbsp;<a href="#n-reporting">Reporting</a></h4><div id="rfc.section.2.2.3.p.1"><p>Some
 versioning information about a resource requires that parameters be 
specified along with that request for information. Included in basic 
versioning is the required support for an extensible reporting 
mechanism, which includes a REPORT method as well as a live property for
 determining what reports are supported by a particular resource. The 
REPORT method is required by versioning, but it can be used in 
non-versioning WebDAV extensions.<a class="self" href="#rfc.section.2.2.3.p.1">¶</a></p></div><div id="rfc.section.2.2.3.p.2"><p>To
 allow a client to query the properties of all versions in the version 
history of a specified version-controlled resource, basic versioning 
provides the DAV:version-tree report (see <a href="#REPORT_version-tree" title="DAV:version-tree Report">Section&nbsp;3.7</a>). A more powerful version history reporting mechanism is provided by applying the DAV:expand-property report (see <a href="#REPORT_expand-property" title="DAV:expand-property Report">Section&nbsp;3.8</a>) to a version history resource (see <a href="#version-history.feature" title="Version-History Feature">Section&nbsp;5</a>).<a class="self" href="#rfc.section.2.2.3.p.2">¶</a></p></div></section></section></section><hr class="noprint"><section id="n-version-control-feature"><h2 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#n-version-control-feature">Version-Control Feature</a></h2><div id="rfc.section.3.p.1"><p>The
 version-control feature provides support for putting a resource under 
version control, creating an associated version-controlled resource and 
version history resource as described in <a href="#creating.a.version-controlled.resource" title="Creating a Version-Controlled Resource">Section&nbsp;2.2.1</a>.
 A server indicates that it supports the version-control feature by 
including the string "version-control" as a field in the DAV header in 
the response to an OPTIONS request. The version-control feature <em class="bcp14">MUST</em> be supported if any other versioning feature is supported.<a class="self" href="#rfc.section.3.p.1">¶</a></p></div><section id="n-additional-resource-properties_1"><h3 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#n-additional-resource-properties_1">Additional Resource Properties</a></h3><div id="rfc.section.3.1.p.1"><p>The version-control feature introduces the following <em class="bcp14">REQUIRED</em> properties for any WebDAV resource.<a class="self" href="#rfc.section.3.1.p.1">¶</a></p></div><section id="PROPERTY_comment"><h4 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#PROPERTY_comment">DAV:comment</a></h4><div id="rfc.section.3.1.1.p.1"><p>This
 property is used to track a brief comment about a resource that is 
suitable for presentation to a user. The DAV:comment of a version can be
 used to indicate why that version was created.<a class="self" href="#rfc.section.3.1.1.p.1">¶</a></p></div><div id="rfc.figure.u.6"><pre class="inline">&lt;!ELEMENT comment (#PCDATA)&gt;
PCDATA value: string
</pre></div></section><section id="PROPERTY_creator-displayname"><h4 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#PROPERTY_creator-displayname">DAV:creator-displayname</a></h4><div id="rfc.section.3.1.2.p.1"><p>This
 property contains a description of the creator of the resource that is 
suitable for presentation to a user. The DAV:creator-displayname of a 
version can be used to indicate who created that version.<a class="self" href="#rfc.section.3.1.2.p.1">¶</a></p></div><div id="rfc.figure.u.7"><pre class="inline">&lt;!ELEMENT creator-displayname (#PCDATA)&gt;
PCDATA value: string
</pre></div></section><section id="PROPERTY_supported-method-set"><h4 id="rfc.section.3.1.3"><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;<a href="#PROPERTY_supported-method-set">DAV:supported-method-set (protected)</a></h4><div id="rfc.section.3.1.3.p.1"><p>This
 property identifies the methods that are supported by the resource. A 
method is supported by a resource if there is some state of that 
resource for which an application of that method will successfully 
satisfy all postconditions of that method, including any additional 
postconditions added by the features supported by that resource.<a class="self" href="#rfc.section.3.1.3.p.1">¶</a></p></div><div id="rfc.figure.u.8"><pre class="inline">&lt;!ELEMENT supported-method-set (supported-method*)&gt;
&lt;!ELEMENT supported-method ANY&gt;
&lt;!ATTLIST supported-method name NMTOKEN #REQUIRED&gt;
name value: a method name
</pre></div></section><section id="PROPERTY_supported-live-property-set"><h4 id="rfc.section.3.1.4"><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;<a href="#PROPERTY_supported-live-property-set">DAV:supported-live-property-set (protected)</a></h4><div id="rfc.section.3.1.4.p.1"><p>This
 property identifies the live properties that are supported by the 
resource. A live property is supported by a resource if that property 
has the semantics defined for that property. The value of this property <em class="bcp14">MUST</em> identify all live properties defined by this document that are supported by the resource, and <em class="bcp14">SHOULD</em> identify all live properties that are supported by the resource.<a class="self" href="#rfc.section.3.1.4.p.1">¶</a></p></div><div id="rfc.figure.u.9"><pre class="inline">&lt;!ELEMENT supported-live-property-set (supported-live-property*)&gt;
&lt;!ELEMENT supported-live-property name&gt;
&lt;!ELEMENT prop ANY&gt;
ANY value: a property element type
</pre></div></section><section id="PROPERTY_supported-report-set"><h4 id="rfc.section.3.1.5"><a href="#rfc.section.3.1.5">3.1.5</a>&nbsp;<a href="#PROPERTY_supported-report-set">DAV:supported-report-set (protected)</a></h4><div id="rfc.section.3.1.5.p.1"><p>This property identifies the reports that are supported by the resource.<a class="self" href="#rfc.section.3.1.5.p.1">¶</a></p></div><div id="rfc.figure.u.10"><pre class="inline">&lt;!ELEMENT supported-report-set (supported-report*)&gt;
&lt;!ELEMENT supported-report report&gt;
&lt;!ELEMENT report ANY&gt;
ANY value: a report element type
</pre></div></section></section><section id="n-version-controlled-resource-properties"><h3 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#n-version-controlled-resource-properties">Version-Controlled Resource Properties</a></h3><div id="rfc.section.3.2.p.1"><p>The version-control feature introduces the following <em class="bcp14">REQUIRED</em> properties for a version-controlled resource.<a class="self" href="#rfc.section.3.2.p.1">¶</a></p></div><section id="PROPERTY_checked-in"><h4 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a href="#PROPERTY_checked-in">DAV:checked-in (protected)</a></h4><div id="rfc.section.3.2.1.p.1"><p>This
 property appears on a checked-in version-controlled resource, and 
identifies a version that has the same content and dead properties as 
the version-controlled resource. This property is removed when the 
resource is checked out, and then added back (identifying a new version)
 when the resource is checked back in.<a class="self" href="#rfc.section.3.2.1.p.1">¶</a></p></div><div id="rfc.figure.u.11"><pre class="inline">&lt;!ELEMENT checked-in (href)&gt;
</pre></div></section><section id="PROPERTY_auto-version"><h4 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a href="#PROPERTY_auto-version">DAV:auto-version</a></h4><div id="rfc.section.3.2.2.p.1"><p>If
 the DAV:auto-version value is DAV:checkout-checkin, when a modification
 request (such as PUT/PROPPATCH) is applied to a checked-in 
version-controlled resource, the request is automatically preceded by a 
checkout and followed by a checkin operation.<a class="self" href="#rfc.section.3.2.2.p.1">¶</a></p></div><div id="rfc.section.3.2.2.p.2"><p>If
 the DAV:auto-version value is DAV:checkout-unlocked-checkin, when a 
modification request is applied to a checked-in version-controlled 
resource, the request is automatically preceded by a checkout operation.
 If the resource is not write-locked, the request is automatically 
followed by a checkin operation.<a class="self" href="#rfc.section.3.2.2.p.2">¶</a></p></div><div id="rfc.section.3.2.2.p.3"><p>If
 the DAV:auto-version value is DAV:checkout, when a modification request
 is applied to a checked-in version-controlled resource, the request is 
automatically preceded by a checkout operation.<a class="self" href="#rfc.section.3.2.2.p.3">¶</a></p></div><div id="rfc.section.3.2.2.p.4"><p>If
 the DAV:auto-version value is DAV:locked-checkout, when a modification 
request is applied to a write-locked checked-in version-controlled 
resource, the request is automatically preceded by a checkout operation.<a class="self" href="#rfc.section.3.2.2.p.4">¶</a></p></div><div id="rfc.section.3.2.2.p.5"><p>If
 an update to a write-locked checked-in resource is automatically 
preceded by a checkout of that resource, the checkout is associated with
 the write lock. When this write lock is removed (e.g. from an UNLOCK or
 a lock timeout), if the resource has not yet been checked in, the 
removal of the write lock is automatically preceded by a checkin 
operation.<a class="self" href="#rfc.section.3.2.2.p.5">¶</a></p></div><div id="rfc.section.3.2.2.p.6"><p>A server <em class="bcp14">MAY</em> refuse to allow the value of the DAV:auto-version property to be modified, or <em class="bcp14">MAY</em> only support values from a subset of the valid values.<a class="self" href="#rfc.section.3.2.2.p.6">¶</a></p></div><div id="rfc.figure.u.12"><pre class="inline">&lt;!ELEMENT auto-version (checkout-checkin | checkout-unlocked-checkin
 | checkout | locked-checkout)? &gt;
&lt;!ELEMENT checkout-checkin EMPTY&gt;
&lt;!ELEMENT checkout-unlocked-checkin EMPTY&gt;
&lt;!ELEMENT checkout EMPTY&gt;
&lt;!ELEMENT locked-checkout EMPTY&gt;
</pre></div></section></section><section id="n-checked-out-resource-properties_1"><h3 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#n-checked-out-resource-properties_1">Checked-Out Resource Properties</a></h3><div id="rfc.section.3.3.p.1"><p>The version-control feature introduces the following <em class="bcp14">REQUIRED</em> properties for a checked-out resource.<a class="self" href="#rfc.section.3.3.p.1">¶</a></p></div><section id="PROPERTY_checked-out"><h4 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a href="#PROPERTY_checked-out">DAV:checked-out (protected)</a></h4><div id="rfc.section.3.3.1.p.1"><p>This
 property identifies the version that was identified by the 
DAV:checked-in property at the time the resource was checked out. This 
property is removed when the resource is checked in.<a class="self" href="#rfc.section.3.3.1.p.1">¶</a></p></div><div id="rfc.figure.u.13"><pre class="inline">&lt;!ELEMENT checked-out (href)&gt;
</pre></div></section><section id="PROPERTY_predecessor-set"><h4 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a href="#PROPERTY_predecessor-set">DAV:predecessor-set</a></h4><div id="rfc.section.3.3.2.p.1"><p>This property determines the DAV:predecessor-set property of the version that results from checking in this resource.<a class="self" href="#rfc.section.3.3.2.p.1">¶</a></p></div><div id="rfc.section.3.3.2.p.2"><p>A server <em class="bcp14">MAY</em> reject attempts to modify the DAV:predecessor-set of a version-controlled resource.<a class="self" href="#rfc.section.3.3.2.p.2">¶</a></p></div><div id="rfc.figure.u.14"><pre class="inline">&lt;!ELEMENT predecessor-set (href+)&gt;
</pre></div></section></section><section id="n-version-properties"><h3 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#n-version-properties">Version Properties</a></h3><div id="rfc.section.3.4.p.1"><p>The version-control feature introduces the following <em class="bcp14">REQUIRED</em> properties for a version.<a class="self" href="#rfc.section.3.4.p.1">¶</a></p></div><section id="n-dav-predecessor-set--protected-"><h4 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a href="#n-dav-predecessor-set--protected-">DAV:predecessor-set (protected)</a></h4><div id="rfc.section.3.4.1.p.1"><p>This
 property identifies each predecessor of this version. Except for the 
root version, which has no predecessors, each version has at least one 
predecessor.<a class="self" href="#rfc.section.3.4.1.p.1">¶</a></p></div><div id="rfc.figure.u.15"><pre class="inline">&lt;!ELEMENT predecessor-set (href*)&gt;
</pre></div></section><section id="PROPERTY_successor-set"><h4 id="rfc.section.3.4.2"><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;<a href="#PROPERTY_successor-set">DAV:successor-set (computed)</a></h4><div id="rfc.section.3.4.2.p.1"><p>This property identifies each version whose DAV:predecessor-set identifies this version.<a class="self" href="#rfc.section.3.4.2.p.1">¶</a></p></div><div id="rfc.figure.u.16"><pre class="inline">&lt;!ELEMENT successor-set (href*)&gt;
</pre></div></section><section id="PROPERTY_checkout-set"><h4 id="rfc.section.3.4.3"><a href="#rfc.section.3.4.3">3.4.3</a>&nbsp;<a href="#PROPERTY_checkout-set">DAV:checkout-set (computed)</a></h4><div id="rfc.section.3.4.3.p.1"><p>This property identifies each checked-out resource whose DAV:checked-out property identifies this version.<a class="self" href="#rfc.section.3.4.3.p.1">¶</a></p></div><div id="rfc.figure.u.17"><pre class="inline">&lt;!ELEMENT checkout-set (href*)&gt;
</pre></div></section><section id="PROPERTY_version-name"><h4 id="rfc.section.3.4.4"><a href="#rfc.section.3.4.4">3.4.4</a>&nbsp;<a href="#PROPERTY_version-name">DAV:version-name (protected)</a></h4><div id="rfc.section.3.4.4.p.1"><p>This
 property contains a server-defined string that is different for each 
version in a given version history. This string is intended for display 
for a user, unlike the URL of a version, which is normally only used by a
 client and not displayed for a user.<a class="self" href="#rfc.section.3.4.4.p.1">¶</a></p></div><div id="rfc.figure.u.18"><pre class="inline">&lt;!ELEMENT version-name (#PCDATA)&gt;
PCDATA value: string
</pre></div></section></section><section id="METHOD_VERSION-CONTROL"><h3 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#METHOD_VERSION-CONTROL">VERSION-CONTROL Method</a></h3><div id="rfc.section.3.5.p.1"><p>A
 VERSION-CONTROL request can be used to create a version-controlled 
resource at the request-URL. It can be applied to a versionable resource
 or to a version-controlled resource.<a class="self" href="#rfc.section.3.5.p.1">¶</a></p></div><div id="rfc.section.3.5.p.2"><p>If
 the request-URL identifies a versionable resource, a new version 
history resource is created, a new version is created whose content and 
dead properties are copied from the versionable resource, and the 
resource is given a DAV:checked-in property that is initialized to 
identify this new version.<a class="self" href="#rfc.section.3.5.p.2">¶</a></p></div><div id="rfc.section.3.5.p.3"><p>If
 the request-URL identifies a version-controlled resource, the resource 
just remains under version-control. This allows a client to be unaware 
of whether or not a server automatically puts a resource under version 
control when it is created.<a class="self" href="#rfc.section.3.5.p.3">¶</a></p></div><div id="rfc.section.3.5.p.4"><p>If a VERSION-CONTROL request fails, the server state preceding the request <em class="bcp14">MUST</em> be restored.<a class="self" href="#rfc.section.3.5.p.4">¶</a></p></div><div id="rfc.section.3.5.p.5"><p><span id="rfc.iref.v.7"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.3.5.p.5">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:version-control XML element. <span id="rfc.figure.u.19"><pre class="inline">&lt;!ELEMENT version-control ANY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em>
 be a DAV:version-control-response XML element. Note that this document 
does not define any elements for the VERSION-CONTROL response body, but 
the DAV:version-control-response element is defined to ensure 
interoperability between future extensions that do define elements for 
the VERSION-CONTROL response body. <span id="rfc.figure.u.20"><pre class="inline">&lt;!ELEMENT version-control-response ANY&gt;
</pre></span> </li></ul></div><div id="rfc.section.3.5.p.6"><p><span id="rfc.iref.v.8"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.3.5.p.6">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.2"></span> <span id="rfc.iref.c.4"></span> (DAV:put-under-version-control): If the request-URL identified a versionable resource at the time of the request, the request <em class="bcp14">MUST</em> have created a new version history and <em class="bcp14">MUST</em> have created a new version resource in that version history. The resource <em class="bcp14">MUST</em>
 have a DAV:checked-in property that identifies the new version. The 
content, dead properties, and DAV:resourcetype of the new version <em class="bcp14">MUST</em>
 be the same as those of the resource. Note that an implementation can 
choose to locate the version history and version resources anywhere that
 it wishes. In particular, it could locate them on the same host and 
server as the version-controlled resource, on a different virtual host 
maintained by the same server, on the same host maintained by a 
different server, or on a different host maintained by a different 
server.</li><li><span id="rfc.iref.d.3"></span> <span id="rfc.iref.c.5"></span>
 (DAV:must-not-change-existing-checked-in-out): If the request-URL 
identified a resource already under version control at the time of the 
request, the request <em class="bcp14">MUST NOT</em> change the DAV:checked-in or DAV:checked-out property of that version-controlled resource.</li></ul></div><section id="n-example---version-control"><h4 id="rfc.section.3.5.1"><a href="#rfc.section.3.5.1">3.5.1</a>&nbsp;<a href="#n-example---version-control">Example - VERSION-CONTROL</a></h4><div id="rfc.figure.u.21"><p>&gt;&gt;REQUEST</p><pre class="text2">VERSION-CONTROL /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.22"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
</pre></div><div id="rfc.section.3.5.1.p.1"><p>In this example, 
/foo.html is put under version control. A new version history is created
 for it, and a new version is created that has a copy of the content and
 dead properties of /foo.html. The DAV:checked-in property of /foo.html 
identifies this new version.<a class="self" href="#rfc.section.3.5.1.p.1">¶</a></p></div></section></section><section id="METHOD_REPORT"><h3 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a href="#METHOD_REPORT">REPORT Method</a></h3><div id="rfc.section.3.6.p.1"><p>A
 REPORT request is an extensible mechanism for obtaining information 
about a resource. Unlike a resource property, which has a single value, 
the value of a report can depend on additional information specified in 
the REPORT request body and in the REPORT request headers.<a class="self" href="#rfc.section.3.6.p.1">¶</a></p></div><div id="rfc.section.3.6.p.2"><p><span id="rfc.iref.r.2"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.3.6.p.2">¶</a></p><ul class="empty"><li>The
 body of a REPORT request specifies which report is being requested, as 
well as any additional information that will be used to customize the 
report.</li><li>The request <em class="bcp14">MAY</em> include a Depth header. If no Depth header is included, Depth:0 is assumed.</li><li>The response body for a successful request <em class="bcp14">MUST</em> contain the requested report.</li><li>If a Depth request header is included, the response <em class="bcp14">MUST</em> be a 207 Multi-Status. The request <em class="bcp14">MUST</em>
 be applied separately to the collection itself and to all members of 
the collection that satisfy the Depth value. The DAV:prop element of a 
DAV:response for a given resource <em class="bcp14">MUST</em> contain the requested report for that resource.</li></ul></div><div id="rfc.section.3.6.p.3"><p><span id="rfc.iref.r.3"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.3.6.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.4"></span> <span id="rfc.iref.c.6"></span> (DAV:supported-report): The specified report <em class="bcp14">MUST</em> be supported by the resource identified by the request-URL.</li></ul></div><div id="rfc.section.3.6.p.4"><p><span id="rfc.iref.r.4"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.3.6.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.5"></span> <span id="rfc.iref.c.7"></span> (DAV:no-modification): The REPORT method <em class="bcp14">MUST NOT</em> have changed the content or dead properties of any resource.</li></ul></div></section><section id="REPORT_version-tree"><h3 id="rfc.section.3.7"><a href="#rfc.section.3.7">3.7</a>&nbsp;<a href="#REPORT_version-tree">DAV:version-tree Report</a></h3><div id="rfc.section.3.7.p.1"><p>The
 DAV:version-tree report describes the requested properties of all the 
versions in the version history of a version. If the report is requested
 for a version-controlled resource, it is redirected to its 
DAV:checked-in or DAV:checked-out version.<a class="self" href="#rfc.section.3.7.p.1">¶</a></p></div><div id="rfc.section.3.7.p.2"><p>The DAV:version-tree report <em class="bcp14">MUST</em> be supported by all version resources and all version-controlled resources.<a class="self" href="#rfc.section.3.7.p.2">¶</a></p></div><div id="rfc.section.3.7.p.3"><p><span id="rfc.iref.d.6"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.3.7.p.3">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:version-tree XML element. <span id="rfc.figure.u.23"><pre class="inline">&lt;!ELEMENT version-tree ANY&gt;
ANY value: a sequence of zero or more elements, with at most one
DAV:prop element.
prop: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.11" id="rfc.xref.RFC2518.4">Section 12.11</a>
</pre></span> </li><li>The response body for a successful request <em class="bcp14">MUST</em> be a DAV:multistatus XML element. <span id="rfc.figure.u.24"><pre class="inline">multistatus: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.9" id="rfc.xref.RFC2518.5">Section 12.9</a>
</pre></span> </li><li>The response body for a successful DAV:version-tree REPORT request <em class="bcp14">MUST</em> contain a DAV:response element for each version in the version history of the version identified by the request-URL.</li></ul></div><section id="n-example---dav-version-tree-report"><h4 id="rfc.section.3.7.1"><a href="#rfc.section.3.7.1">3.7.1</a>&nbsp;<a href="#n-example---dav-version-tree-report">Example - DAV:version-tree Report</a></h4><div id="rfc.section.3.7.1.p.1"><p>The version history drawn below would produce the following version tree report.<a class="self" href="#rfc.section.3.7.1.p.1">¶</a></p></div><div id="rfc.figure.u.25"><pre class="drawing">                  foo.html History

                       ┌───┐
                       │   │ V1
                       └───┘
                      /     \
                     /       \
                 ┌───┐       ┌───┐
                 │   │ V2    │   │ V2.1.1
                 └───┘       └───┘
</pre></div><div id="rfc.figure.u.26"><p>&gt;&gt;REQUEST</p><pre class="text2">REPORT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:version-tree xmlns:D="DAV:"&gt;
 &lt;D:prop&gt;
   &lt;D:version-name/&gt;
   &lt;D:creator-displayname/&gt;
   &lt;D:successor-set/&gt;
 &lt;/D:prop&gt;
&lt;/D:version-tree&gt;
</pre></div><div id="rfc.figure.u.27"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:multistatus xmlns:D="DAV:"&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/23/ver/V1&lt;/D:href&gt;
   &lt;D:propstat&gt;
     &lt;D:prop&gt;
       &lt;D:version-name&gt;V1&lt;/D:version-name&gt;
       &lt;D:creator-displayname&gt;Fred&lt;/D:creator-displayname&gt;
       &lt;D:successor-set&gt;
         &lt;D:href&gt;http://repo.webdav.org/his/23/ver/V2&lt;/D:href&gt;
         &lt;D:href&gt;http://repo.webdav.org/his/23/ver/V2.1.1&lt;/D:href&gt;
       &lt;/D:successor-set&gt;
     &lt;/D:prop&gt;
     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
   &lt;/D:propstat&gt;
 &lt;/D:response&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/23/ver/V2&lt;/D:href&gt;
   &lt;D:propstat&gt;
     &lt;D:prop&gt;
       &lt;D:version-name&gt;V2&lt;/D:version-name&gt;
       &lt;D:creator-displayname&gt;Fred&lt;/D:creator-displayname&gt;
       &lt;D:successor-set/&gt;
     &lt;/D:prop&gt;
     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
   &lt;/D:propstat&gt;
 &lt;/D:response&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/23/ver/V2.1.1&lt;/D:href&gt;
   &lt;D:propstat&gt;
     &lt;D:prop&gt;
       &lt;D:version-name&gt;V2.1.1&lt;/D:version-name&gt;
       &lt;D:creator-displayname&gt;Sally&lt;/D:creator-displayname&gt;
       &lt;D:successor-set/&gt;
     &lt;/D:prop&gt;
     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
   &lt;/D:propstat&gt;
 &lt;/D:response&gt;
&lt;/D:multistatus&gt;
</pre></div></section></section><section id="REPORT_expand-property"><h3 id="rfc.section.3.8"><a href="#rfc.section.3.8">3.8</a>&nbsp;<a href="#REPORT_expand-property">DAV:expand-property Report</a></h3><div id="rfc.section.3.8.p.1"><p>Many
 property values are defined as a DAV:href, or a set of DAV:href 
elements. The DAV:expand-property report provides a mechanism for 
retrieving in one request the properties from the resources identified 
by those DAV:href elements. This report not only decreases the number of
 requests required, but also allows the server to minimize the number of
 separate read transactions required on the underlying versioning store.<a class="self" href="#rfc.section.3.8.p.1">¶</a></p></div><div id="rfc.section.3.8.p.2"><p>The DAV:expand-property report <em class="bcp14">SHOULD</em> be supported by all resources that support the REPORT method.<a class="self" href="#rfc.section.3.8.p.2">¶</a></p></div><div id="rfc.section.3.8.p.3"><p><span id="rfc.iref.d.7"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.3.8.p.3">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:expand-property XML element. <span id="rfc.figure.u.28"><pre class="inline">&lt;!ELEMENT expand-property (property*)&gt;
&lt;!ELEMENT property (property*)&gt;
&lt;!ATTLIST property name NMTOKEN #REQUIRED&gt;
name value: a property element type
&lt;!ATTLIST property namespace NMTOKEN "DAV:"&gt;
namespace value: an XML namespace
</pre></span> </li><li>The response body for a successful request <em class="bcp14">MUST</em> be a DAV:multistatus XML element. <span id="rfc.figure.u.29"><pre class="inline">multistatus: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.9" id="rfc.xref.RFC2518.6">Section 12.9</a>
</pre></span> </li><li>The properties reported in the DAV:prop elements of the DAV:multistatus element <em class="bcp14">MUST</em>
 be those identified by the DAV:property elements in the 
DAV:expand-property element. If there are DAV:property elements nested 
within a DAV:property element, then every DAV:href in the value of the 
corresponding property is replaced by a DAV:response element whose 
DAV:prop elements report the values of the properties identified by the 
nested DAV:property elements. The nested DAV:property elements can in 
turn contain DAV:property elements, so that multiple levels of DAV:href 
expansion can be requested.</li><li>Note that a validating parser <em class="bcp14">MUST</em>
 be aware that the DAV:expand-property report effectively modifies the 
DTD of every property by replacing every occurrence of "href" in the DTD
 with "href | response".</li></ul></div><section id="n-example---dav-expand-property"><h4 id="rfc.section.3.8.1"><a href="#rfc.section.3.8.1">3.8.1</a>&nbsp;<a href="#n-example---dav-expand-property">Example - DAV:expand-property</a></h4><div id="rfc.section.3.8.1.p.1"><p>This
 example describes how to query a version-controlled resource to 
determine the DAV:creator-display-name and DAV:activity-set of every 
version in the version history of that version-controlled resource. This
 example assumes that the server supports the version-history feature 
(see <a href="#version-history.feature" title="Version-History Feature">Section&nbsp;5</a>).<a class="self" href="#rfc.section.3.8.1.p.1">¶</a></p></div><div id="rfc.figure.u.30"><p>&gt;&gt;REQUEST</p><pre class="text2">REPORT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:expand-property xmlns:D="DAV:"&gt;
 &lt;D:property name="version-history"&gt;
   &lt;D:property name="version-set"&gt;
     &lt;D:property name="creator-displayname"/&gt;
     &lt;D:property name="activity-set"/&gt;
   &lt;/D:property&gt;
 &lt;/D:property&gt;
&lt;/D:expand-property&gt;
</pre></div><div id="rfc.figure.u.31"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:multistatus xmlns:D="DAV:"&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://www.webdav.org/foo.html&lt;/D:href&gt;
   &lt;D:propstat&gt;
     &lt;D:prop&gt;
       &lt;D:version-history&gt;
         &lt;D:response&gt;
           &lt;D:href&gt;http://repo.webdav.org/his/23&lt;/D:href&gt;
           &lt;D:propstat&gt;
             &lt;D:prop&gt;
               &lt;D:version-set&gt;
                 &lt;D:response&gt;
&lt;D:href&gt;http://repo.webdav.org/his/23/ver/1&lt;/D:href&gt;
                   &lt;D:propstat&gt;
                     &lt;D:prop&gt;
&lt;D:creator-displayname&gt;Fred&lt;/D:creator-displayname&gt;
                       &lt;D:activity-set&gt; &lt;D:href&gt;
                         http://www.webdav.org/ws/dev/sally
                       &lt;/D:href&gt; &lt;/D:activity-set&gt; &lt;/D:prop&gt;
                     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
                   &lt;/D:propstat&gt; &lt;/D:response&gt;
                 &lt;D:response&gt;
&lt;D:href&gt;http://repo.webdav.org/his/23/ver/2&lt;/D:href&gt;
                   &lt;D:propstat&gt;
                     &lt;D:prop&gt;
&lt;D:creator-displayname&gt;Sally&lt;/D:creator-displayname&gt;
                       &lt;D:activity-set&gt;
&lt;D:href&gt;http://repo.webdav.org/act/add-refresh-cmd&lt;/D:href&gt;
                       &lt;/D:activity-set&gt; &lt;/D:prop&gt;
                     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
                   &lt;/D:propstat&gt; &lt;/D:response&gt;
               &lt;/D:version-set&gt; &lt;/D:prop&gt;
             &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
           &lt;/D:propstat&gt; &lt;/D:response&gt;
       &lt;/D:version-history&gt; &lt;/D:prop&gt;
     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
   &lt;/D:propstat&gt; &lt;/D:response&gt;
&lt;/D:multistatus&gt;
</pre></div><div id="rfc.section.3.8.1.p.2"><p>In this example, the 
DAV:creator-displayname and DAV:activity-set properties of the versions 
in the DAV:version-set of the DAV:version-history of 
http://www.webdav.org/foo.html are reported.<a class="self" href="#rfc.section.3.8.1.p.2">¶</a></p></div></section></section><section id="n-additional-options-semantics_1"><h3 id="rfc.section.3.9"><a href="#rfc.section.3.9">3.9</a>&nbsp;<a href="#n-additional-options-semantics_1">Additional OPTIONS Semantics</a></h3><div id="rfc.section.3.9.p.1"><p>If the server supports the version-control feature, it <em class="bcp14">MUST</em>
 include "version-control" as a field in the DAV response header from an
 OPTIONS request on any resource that supports any versioning 
properties, reports, or methods.<a class="self" href="#rfc.section.3.9.p.1">¶</a></p></div></section><section id="additional.put.semantics"><h3 id="rfc.section.3.10"><a href="#rfc.section.3.10">3.10</a>&nbsp;<a href="#additional.put.semantics">Additional PUT Semantics</a></h3><div id="rfc.section.3.10.p.1"><p><span id="rfc.iref.p.2"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.10.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.8"></span> <span id="rfc.iref.c.8"></span>
 (DAV:cannot-modify-version-controlled-content): If the request-URL 
identifies a resource with a DAV:checked-in property, the request <em class="bcp14">MUST</em> fail unless DAV:auto-version semantics will automatically check out the resource.</li><li><span id="rfc.iref.d.9"></span> <span id="rfc.iref.c.9"></span> (DAV:cannot-modify-version): If the request-URL identifies a version, the request <em class="bcp14">MUST</em> fail.</li><li>If
 the request creates a new resource that is automatically placed under 
version control, all preconditions for VERSION-CONTROL apply to the 
request.</li></ul></div><div id="rfc.section.3.10.p.2"><p><span id="rfc.iref.p.3"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.10.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.10"></span> <span id="rfc.iref.c.10"></span>
 (DAV:auto-checkout): If the resource was a checked-in 
version-controlled resource whose DAV:auto-version property indicates it
 should be automatically checked out but not automatically checked in 
for a modification request, then the server <em class="bcp14">MUST</em> 
have automatically checked out the resource prior to executing the 
request. In particular, the value of the DAV:checked-out property of the
 resource <em class="bcp14">MUST</em> be that of the DAV:checked-in property prior to the request, the DAV:checked-in property <em class="bcp14">MUST</em> have been removed, and the DAV:predecessor-set property <em class="bcp14">MUST</em>
 be initialized to be the same as the DAV:checked-out property. If any 
part of the checkout/update sequence failed, the status from the failed 
part of the request <em class="bcp14">MUST</em> be returned, and the server state preceding the request sequence <em class="bcp14">MUST</em> be restored.</li><li><span id="rfc.iref.d.11"></span> <span id="rfc.iref.c.11"></span>
 (DAV:auto-checkout-checkin): If the resource was a checked-in 
version-controlled resource whose DAV:auto-version property indicates it
 should be automatically checked out and automatically checked in for a 
modification request, then the server <em class="bcp14">MUST</em> have 
automatically checked out the resource prior to executing the request 
and automatically checked it in after the request. In particular, the 
DAV:checked-in property of the resource <em class="bcp14">MUST</em> 
identify a new version whose content and dead properties are the same as
 those of the resource. The DAV:predecessor-set of the new version <em class="bcp14">MUST</em>
 identify the version identified by the DAV:checked-in property prior to
 the request. If any part of the checkout/update/checkin sequence 
failed, the status from the failed part of the request <em class="bcp14">MUST</em> be returned, and the server state preceding the request sequence <em class="bcp14">MUST</em> be restored.</li><li>If the request creates a new resource, the new resource <em class="bcp14">MAY</em> have automatically been placed under version control, and all postconditions for VERSION-CONTROL apply to the request.</li></ul></div></section><section id="n-additional-propfind-semantics_1"><h3 id="rfc.section.3.11"><a href="#rfc.section.3.11">3.11</a>&nbsp;<a href="#n-additional-propfind-semantics_1">Additional PROPFIND Semantics</a></h3><div id="rfc.section.3.11.p.1"><p>A DAV:allprop PROPFIND request <em class="bcp14">SHOULD NOT</em>
 return any of the properties defined by this document. This allows a 
versioning server to perform efficiently when a naive client, which does
 not understand the cost of asking a server to compute all possible live
 properties, issues a DAV:allprop PROPFIND request.<a class="self" href="#rfc.section.3.11.p.1">¶</a></p></div><div id="rfc.section.3.11.p.2"><p><span id="rfc.iref.p.4"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.11.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.12"></span> <span id="rfc.iref.c.12"></span>
 (DAV:supported-live-property): If the request attempts to access a 
property defined by this document, the semantics of that property <em class="bcp14">MUST</em> be supported by the server.</li></ul></div></section><section id="n-additional-proppatch-semantics"><h3 id="rfc.section.3.12"><a href="#rfc.section.3.12">3.12</a>&nbsp;<a href="#n-additional-proppatch-semantics">Additional PROPPATCH Semantics</a></h3><div id="rfc.section.3.12.p.1"><p><span id="rfc.iref.p.5"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.12.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.13"></span> <span id="rfc.iref.c.13"></span> (DAV:cannot-modify-version-controlled-property): If the request attempts to modify a dead property, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li><li><span id="rfc.iref.d.14"></span> <span id="rfc.iref.c.14"></span> (DAV:cannot-modify-version): If the request attempts to modify a dead property, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li><li><span id="rfc.iref.d.15"></span> <span id="rfc.iref.c.15"></span>
 (DAV:cannot-modify-protected-property): An attempt to modify a property
 that is defined by this document, as being protected for that kind of 
resource, <em class="bcp14">MUST</em> fail.</li><li><span id="rfc.iref.d.16"></span> <span id="rfc.iref.c.16"></span>
 (DAV:supported-live-property): An attempt to modify a property defined 
by this document, but whose semantics are not enforced by the server, <em class="bcp14">MUST</em>
 fail. This helps ensure that a client will be notified when it is 
trying to use a property whose semantics are not supported by the 
server.</li></ul></div><div id="rfc.section.3.12.p.2"><p><span id="rfc.iref.p.6"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.12.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.17"></span> <span id="rfc.iref.c.17"></span> (DAV:auto-checkout): If the request modified a dead property, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li><li><span id="rfc.iref.d.18"></span> <span id="rfc.iref.c.18"></span> (DAV:auto-checkout-checkin): If the request modified a dead property, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li></ul></div></section><section id="additional.delete.semantics"><h3 id="rfc.section.3.13"><a href="#rfc.section.3.13">3.13</a>&nbsp;<a href="#additional.delete.semantics">Additional DELETE Semantics</a></h3><div id="rfc.section.3.13.p.1"><p><span id="rfc.iref.d.19"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.13.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.20"></span> <span id="rfc.iref.c.19"></span> (DAV:no-version-delete): A server <em class="bcp14">MAY</em> fail an attempt to DELETE a version.</li></ul></div><div id="rfc.section.3.13.p.2"><p><span id="rfc.iref.d.21"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.13.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.22"></span> <span id="rfc.iref.c.20"></span> (DAV:update-predecessor-set): If a version was deleted, the server <em class="bcp14">MUST</em>
 have replaced any reference to that version in a DAV:predecessor-set by
 a copy of the DAV:predecessor-set of the deleted version.</li></ul></div></section><section id="n-additional-copy-semantics_1"><h3 id="rfc.section.3.14"><a href="#rfc.section.3.14">3.14</a>&nbsp;<a href="#n-additional-copy-semantics_1">Additional COPY Semantics</a></h3><div id="rfc.section.3.14.p.1"><p><span id="rfc.iref.c.21"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.14.p.1">¶</a></p><ul class="empty"><li>If
 the request creates a new resource that is automatically placed under 
version control, all preconditions for VERSION-CONTROL apply to the 
request.</li></ul></div><div id="rfc.section.3.14.p.2"><p><span id="rfc.iref.c.22"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.14.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.23"></span> <span id="rfc.iref.c.23"></span> (DAV:must-not-copy-versioning-property): A property defined by this document <em class="bcp14">MUST NOT</em> have been copied to the new resource created by this request, but instead that property of the new resource <em class="bcp14">MUST</em>
 have the default initial value it would have had if the new resource 
had been created by a non-versioning method such as PUT or a MKCOL.</li><li><span id="rfc.iref.d.24"></span> <span id="rfc.iref.c.24"></span> (DAV:auto-checkout): If the destination is a version-controlled resource, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li><li><span id="rfc.iref.d.25"></span> <span id="rfc.iref.c.25"></span> (DAV:auto-checkout-checkin): If the destination is a version-controlled resource, same semantics as PUT (see <a href="#additional.put.semantics" title="Additional PUT Semantics">Section&nbsp;3.10</a>).</li><li><span id="rfc.iref.d.26"></span> <span id="rfc.iref.c.26"></span>
 (DAV:copy-creates-new-resource): If the source of a COPY is a 
version-controlled resource or version, and if there is no resource at 
the destination of the COPY, then the COPY creates a new 
non-version-controlled resource at the destination of the COPY. The new 
resource <em class="bcp14">MAY</em> automatically be put under version control, but the resulting version-controlled resource <em class="bcp14">MUST</em>
 be associated with a new version history created for that new 
version-controlled resource, and all postconditions for VERSION-CONTROL 
apply to the request.</li></ul></div></section><section id="n-additional-move-semantics_1"><h3 id="rfc.section.3.15"><a href="#rfc.section.3.15">3.15</a>&nbsp;<a href="#n-additional-move-semantics_1">Additional MOVE Semantics</a></h3><div id="rfc.section.3.15.p.1"><p><span id="rfc.iref.m.2"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.15.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.27"></span> <span id="rfc.iref.c.27"></span> (DAV:cannot-rename-version): If the request-URL identifies a version, the request <em class="bcp14">MUST</em> fail.</li></ul></div><div id="rfc.section.3.15.p.2"><p><span id="rfc.iref.m.3"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.15.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.28"></span> <span id="rfc.iref.c.28"></span>
 (DAV:preserve-versioning-properties): When a resource is moved from a 
source URL to a destination URL, a property defined by this document <em class="bcp14">MUST</em> have the same value at the destination URL as it had at the source URL.</li></ul></div></section><section id="n-additional-unlock-semantics"><h3 id="rfc.section.3.16"><a href="#rfc.section.3.16">3.16</a>&nbsp;<a href="#n-additional-unlock-semantics">Additional UNLOCK Semantics</a></h3><div id="rfc.section.3.16.p.1"><p>Note
 that these semantics apply both to an explicit UNLOCK request, as well 
as to the removal of a lock because of a lock timeout. If a precondition
 or postcondition cannot be satisfied, the lock timeout <em class="bcp14">MUST NOT</em> occur.<a class="self" href="#rfc.section.3.16.p.1">¶</a></p></div><div id="rfc.section.3.16.p.2"><p><span id="rfc.iref.u.1"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.3.16.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.29"></span> <span id="rfc.iref.c.29"></span>
 (DAV:version-history-is-tree): If the request-URL identifies a 
checked-out version-controlled resource that will be automatically 
checked in when the lock is removed, then the versions identified by the
 DAV:predecessor-set of the checked-out resource <em class="bcp14">MUST</em> be descendants of the root version of the version history for the DAV:checked-out version.</li></ul></div><div id="rfc.section.3.16.p.3"><p><span id="rfc.iref.u.2"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.3.16.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.30"></span> <span id="rfc.iref.c.30"></span>
 (DAV:auto-checkin): If the request-URL identified a checked-out 
version-controlled resource that had been automatically checked out 
because of its DAV:auto-version property, the request <em class="bcp14">MUST</em> have created a new version in the version history of the DAV:checked-out version. The request <em class="bcp14">MUST</em> have allocated a URL for the version that <em class="bcp14">MUST NOT</em> have previously identified any other resource, and <em class="bcp14">MUST NOT</em>
 ever identify a resource other than this version. The content, dead 
properties, DAV:resourcetype, and DAV:predecessor-set of the new version
 <em class="bcp14">MUST</em> be copied from the checked-out resource. The DAV:version-name of the new version <em class="bcp14">MUST</em>
 be set to a server-defined value distinct from all other 
DAV:version-name values of other versions in the same version history. 
The request <em class="bcp14">MUST</em> have removed the DAV:checked-out property of the version-controlled resource, and <em class="bcp14">MUST</em> have added a DAV:checked-in property that identifies the new version.</li></ul></div></section></section><hr class="noprint"><section id="checkout-in-place.feature"><h2 id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#checkout-in-place.feature">CHECKOUT-IN-PLACE FEATURE</a></h2><div id="rfc.section.4.p.1"><p>With
 the version-control feature, WebDAV locking can be used to avoid the 
proliferation of versions that would result if every modification to a 
version-controlled resource produced a new version. The 
checkout-in-place feature provides an alternative mechanism that allows a
 client to explicitly check out and check in a resource to create a new 
version.<a class="self" href="#rfc.section.4.p.1">¶</a></p></div><section id="n-additional-version-properties_1"><h3 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#n-additional-version-properties_1">Additional Version Properties</a></h3><div id="rfc.section.4.1.p.1"><p>The checkout-in-place feature introduces the following <em class="bcp14">REQUIRED</em> properties for a version.<a class="self" href="#rfc.section.4.1.p.1">¶</a></p></div><section id="PROPERTY_checkout-fork"><h4 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a href="#PROPERTY_checkout-fork">DAV:checkout-fork</a></h4><div id="rfc.section.4.1.1.p.1"><p>This
 property controls the behavior of CHECKOUT when a version already is 
checked out or has a successor. If the DAV:checkout-fork of a version is
 DAV:forbidden, a CHECKOUT request <em class="bcp14">MUST</em> fail if 
it would result in that version appearing in the DAV:predecessor-set or 
DAV:checked-out property of more than one version or checked-out 
resource. If DAV:checkout-fork is DAV:discouraged, such a CHECKOUT 
request <em class="bcp14">MUST</em> fail unless DAV:fork-ok is specified in the CHECKOUT request body.<a class="self" href="#rfc.section.4.1.1.p.1">¶</a></p></div><div id="rfc.section.4.1.1.p.2"><p>A server <em class="bcp14">MAY</em> reject attempts to modify the DAV:checkout-fork of a version. <a class="self" href="#rfc.section.4.1.1.p.2">¶</a></p><span id="rfc.figure.u.32"><pre class="inline">&lt;!ELEMENT checkout-fork ANY&gt;
ANY value: A sequence of elements with at most one DAV:discouraged
or DAV:forbidden element.
&lt;!ELEMENT discouraged EMPTY&gt;
&lt;!ELEMENT forbidden EMPTY&gt;
</pre></span></div></section><section id="PROPERTY_checkin-fork"><h4 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a href="#PROPERTY_checkin-fork">DAV:checkin-fork</a></h4><div id="rfc.section.4.1.2.p.1"><p>This
 property controls the behavior of CHECKIN when a version already has a 
successor. If the DAV:checkin-fork of a version is DAV:forbidden, a 
CHECKIN request <em class="bcp14">MUST</em> fail if it would result in 
that version appearing in the DAV:predecessor-set of more than one 
version. If DAV:checkin-fork is DAV:discouraged, such a CHECKIN request <em class="bcp14">MUST</em> fail unless DAV:fork-ok is specified in the CHECKIN request body.<a class="self" href="#rfc.section.4.1.2.p.1">¶</a></p></div><div id="rfc.section.4.1.2.p.2"><p>A server <em class="bcp14">MAY</em> reject attempts to modify the DAV:checkout-fork of a version. <a class="self" href="#rfc.section.4.1.2.p.2">¶</a></p><span id="rfc.figure.u.33"><pre class="inline">&lt;!ELEMENT checkin-fork ANY&gt;
ANY value: A sequence of elements with at most one DAV:discouraged
or DAV:forbidden element.
&lt;!ELEMENT discouraged EMPTY&gt;
&lt;!ELEMENT forbidden EMPTY&gt;
</pre></span></div></section></section><section id="n-checked-out-resource-properties_2"><h3 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#n-checked-out-resource-properties_2">Checked-Out Resource Properties</a></h3><div id="rfc.section.4.2.p.1"><p>The checkout-in-place feature introduces the following <em class="bcp14">REQUIRED</em> properties for a checked-out resource.<a class="self" href="#rfc.section.4.2.p.1">¶</a></p></div><section id="n-dav-checkout-fork_1"><h4 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#n-dav-checkout-fork_1">DAV:checkout-fork</a></h4><div id="rfc.section.4.2.1.p.1"><p>This property determines the DAV:checkout-fork property of the version that results from checking in this resource.<a class="self" href="#rfc.section.4.2.1.p.1">¶</a></p></div></section><section id="n-dav-checkin-fork_1"><h4 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#n-dav-checkin-fork_1">DAV:checkin-fork</a></h4><div id="rfc.section.4.2.2.p.1"><p>This property determines the DAV:checkin-fork property of the version that results from checking in this resource.<a class="self" href="#rfc.section.4.2.2.p.1">¶</a></p></div></section></section><section id="checkout.method.applied.to.a.version-controlled.resource"><h3 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#checkout.method.applied.to.a.version-controlled.resource">CHECKOUT Method (applied to a version-controlled resource)</a></h3><div id="rfc.section.4.3.p.1"><p>A
 CHECKOUT request can be applied to a checked-in version-controlled 
resource to allow modifications to the content and dead properties of 
that version-controlled resource.<a class="self" href="#rfc.section.4.3.p.1">¶</a></p></div><div id="rfc.section.4.3.p.2"><p>If a CHECKOUT request fails, the server state preceding the request <em class="bcp14">MUST</em> be restored.<a class="self" href="#rfc.section.4.3.p.2">¶</a></p></div><div id="rfc.section.4.3.p.3"><p><span id="rfc.iref.c.31"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.4.3.p.3">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:checkout XML element. <span id="rfc.figure.u.34"><pre class="inline">&lt;!ELEMENT checkout ANY&gt;
</pre></span> </li><li>ANY value: A sequence of elements with at most one DAV:fork-ok element. <span id="rfc.figure.u.35"><pre class="inline">&lt;!ELEMENT fork-ok EMPTY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:checkout-response XML element. <span id="rfc.figure.u.36"><pre class="inline">&lt;!ELEMENT checkout-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.4.3.p.4"><p><span id="rfc.iref.c.32"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.4.3.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.31"></span> <span id="rfc.iref.c.33"></span> (DAV:must-be-checked-in): If a version-controlled resource is being checked out, it <em class="bcp14">MUST</em> have a DAV:checked-in property.</li><li><span id="rfc.iref.d.32"></span> <span id="rfc.iref.c.34"></span>
 (DAV:checkout-of-version-with-descendant-is-forbidden): If the 
DAV:checkout-fork property of the version being checked out is 
DAV:forbidden, the request <em class="bcp14">MUST</em> fail if a version identifies that version in its DAV:predecessor-set.</li><li><span id="rfc.iref.d.33"></span> <span id="rfc.iref.c.35"></span>
 (DAV:checkout-of-version-with-descendant-is-discouraged): If the 
DAV:checkout-fork property of the version being checked out is 
DAV:discouraged, the request <em class="bcp14">MUST</em> fail if a version identifies that version in its DAV:predecessor-set unless DAV:fork-ok is specified in the request body.</li><li><span id="rfc.iref.d.34"></span> <span id="rfc.iref.c.36"></span>
 (DAV:checkout-of-checked-out-version-is-forbidden): If the 
DAV:checkout-fork property of the version being checked out is 
DAV:forbidden, the request <em class="bcp14">MUST</em> fail if a checked-out resource identifies that version in its DAV:checked-out property.</li><li><span id="rfc.iref.d.35"></span> <span id="rfc.iref.c.37"></span>
 (DAV:checkout-of-checked-out-version-is-discouraged): If the 
DAV:checkout-fork property of the version being checked out is 
DAV:discouraged, the request <em class="bcp14">MUST</em> fail if a 
checked-out resource identifies that version in its DAV:checked-out 
property unless DAV:fork-ok is specified in the request body.</li></ul></div><div id="rfc.section.4.3.p.5"><p><span id="rfc.iref.c.38"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.4.3.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.36"></span> <span id="rfc.iref.c.39"></span> (DAV:is-checked-out): The checked-out resource <em class="bcp14">MUST</em>
 have a DAV:checked-out property that identifies the DAV:checked-in 
version preceding the checkout. The version-controlled resource <em class="bcp14">MUST NOT</em> have a DAV:checked-in property.</li><li><span id="rfc.iref.d.37"></span> <span id="rfc.iref.c.40"></span> (DAV:initialize-predecessor-set): The DAV:predecessor-set property of the checked-out resource <em class="bcp14">MUST</em> be initialized to be the DAV:checked-out version.</li></ul></div><section id="n-example---checkout-of-a-version-controlled-resource"><h4 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a href="#n-example---checkout-of-a-version-controlled-resource">Example - CHECKOUT of a version-controlled resource</a></h4><div id="rfc.figure.u.37"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKOUT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.38"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Cache-Control: no-cache
</pre></div><div id="rfc.section.4.3.1.p.1"><p>In this example, the version-controlled resource /foo.html is checked out.<a class="self" href="#rfc.section.4.3.1.p.1">¶</a></p></div></section></section><section id="checkin.method.applied.to.a.version-controlled.resource"><h3 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#checkin.method.applied.to.a.version-controlled.resource">CHECKIN Method (applied to a version-controlled resource)</a></h3><div id="rfc.section.4.4.p.1"><p>A
 CHECKIN request can be applied to a checked-out version-controlled 
resource to produce a new version whose content and dead properties are 
copied from the checked-out resource.<a class="self" href="#rfc.section.4.4.p.1">¶</a></p></div><div id="rfc.section.4.4.p.2"><p>If a CHECKIN request fails, the server state preceding the request <em class="bcp14">MUST</em> be restored.<a class="self" href="#rfc.section.4.4.p.2">¶</a></p></div><div id="rfc.section.4.4.p.3"><p><span id="rfc.iref.c.41"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.4.4.p.3">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:checkin XML element. <span id="rfc.figure.u.39"><pre class="inline">&lt;!ELEMENT checkin ANY&gt;
ANY value: A sequence of elements with at most one
DAV:keep-checked-out element and at most one DAV:fork-ok element.

&lt;!ELEMENT keep-checked-out EMPTY&gt;
&lt;!ELEMENT fork-ok EMPTY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:checkin-response XML element. <span id="rfc.figure.u.40"><pre class="inline">&lt;!ELEMENT checkin-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.4.4.p.4"><p><span id="rfc.iref.c.42"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.4.4.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.38"></span> <span id="rfc.iref.c.43"></span> (DAV:must-be-checked-out): The request-URL <em class="bcp14">MUST</em> identify a resource with a DAV:checked-out property.</li><li><span id="rfc.iref.d.39"></span> <span id="rfc.iref.c.44"></span> (DAV:version-history-is-tree) The versions identified by the DAV:predecessor-set of the checked-out resource <em class="bcp14">MUST</em> be descendants of the root version of the version history for the DAV:checked-out version.</li><li><span id="rfc.iref.d.40"></span> <span id="rfc.iref.c.45"></span> (DAV:checkin-fork-forbidden): A CHECKIN request <em class="bcp14">MUST</em>
 fail if it would cause a version whose DAV:checkin-fork is 
DAV:forbidden to appear in the DAV:predecessor-set of more than one 
version.</li><li><span id="rfc.iref.d.41"></span> <span id="rfc.iref.c.46"></span> (DAV:checkin-fork-discouraged): A CHECKIN request <em class="bcp14">MUST</em>
 fail if it would cause a version whose DAV:checkin-fork is 
DAV:discouraged to appear in the DAV:predecessor-set of more than one 
version, unless DAV:fork-ok is specified in the request body.</li></ul></div><div id="rfc.section.4.4.p.5"><p><span id="rfc.iref.c.47"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.4.4.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.42"></span> <span id="rfc.iref.c.48"></span> (DAV:create-version): The request <em class="bcp14">MUST</em> have created a new version in the version history of the DAV:checked-out version. The request <em class="bcp14">MUST</em> have allocated a distinct new URL for the new version, and that URL <em class="bcp14">MUST NOT</em> ever identify any resource other than that version. The URL for the new version <em class="bcp14">MUST</em> be returned in a Location response header.</li><li><span id="rfc.iref.d.43"></span> <span id="rfc.iref.c.49"></span>
 (DAV:initialize-version-content-and-properties): The content, dead 
properties, DAV:resourcetype, and DAV:predecessor-set of the new version
 <em class="bcp14">MUST</em> be copied from the checked-out resource. The DAV:version-name of the new version <em class="bcp14">MUST</em> be set to a server-defined value distinct from all other DAV:version-name values of other versions in the same version history.</li><li><span id="rfc.iref.d.44"></span> <span id="rfc.iref.c.50"></span>
 (DAV:checked-in): If the request-URL identifies a version-controlled 
resource and DAV:keep-checked-out is not specified in the request body, 
the DAV:checked-out property of the version-controlled resource <em class="bcp14">MUST</em> have been removed and a DAV:checked-in property that identifies the new version <em class="bcp14">MUST</em> have been added.</li><li><span id="rfc.iref.d.45"></span> <span id="rfc.iref.c.51"></span>
 (DAV:keep-checked-out): If DAV:keep-checked-out is specified in the 
request body, the DAV:checked-out property of the checked-out resource <em class="bcp14">MUST</em> have been updated to identify the new version.</li></ul></div><section id="n-example---checkin"><h4 id="rfc.section.4.4.1"><a href="#rfc.section.4.4.1">4.4.1</a>&nbsp;<a href="#n-example---checkin">Example - CHECKIN</a></h4><div id="rfc.figure.u.41"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKIN /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.42"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Location: http://repo.webdav.org/his/23/ver/32
Cache-Control: no-cache
</pre></div><div id="rfc.section.4.4.1.p.1"><p>In this example, 
version-controlled resource /foo.html is checked in, and a new version 
is created at http://repo.webdav.org/his/23/ver/32.<a class="self" href="#rfc.section.4.4.1.p.1">¶</a></p></div></section></section><section id="METHOD_UNCHECKOUT"><h3 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a href="#METHOD_UNCHECKOUT">UNCHECKOUT Method</a></h3><div id="rfc.section.4.5.p.1"><p>An
 UNCHECKOUT request can be applied to a checked-out version-controlled 
resource to cancel the CHECKOUT and restore the pre-CHECKOUT state of 
the version-controlled resource.<a class="self" href="#rfc.section.4.5.p.1">¶</a></p></div><div id="rfc.section.4.5.p.2"><p>If an UNCHECKOUT request fails, the server <em class="bcp14">MUST</em> undo any partial effects of the UNCHECKOUT request.<a class="self" href="#rfc.section.4.5.p.2">¶</a></p></div><div id="rfc.section.4.5.p.3"><p><span id="rfc.iref.u.3"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.4.5.p.3">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:uncheckout XML element. <span id="rfc.figure.u.43"><pre class="inline">&lt;!ELEMENT uncheckout ANY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:uncheckout-response XML element. <span id="rfc.figure.u.44"><pre class="inline">&lt;!ELEMENT uncheckout-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.4.5.p.4"><p><span id="rfc.iref.u.4"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.4.5.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.46"></span> <span id="rfc.iref.c.52"></span> (DAV:must-be-checked-out-version-controlled-resource): The request-URL <em class="bcp14">MUST</em> identify a version-controlled resource with a DAV:checked-out property.</li></ul></div><div id="rfc.section.4.5.p.5"><p><span id="rfc.iref.u.5"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.4.5.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.47"></span> <span id="rfc.iref.c.53"></span>
 (DAV:cancel-checked-out): The value of the DAV:checked-in property is 
that of the DAV:checked-out property prior to the request, and the 
DAV:checked-out property has been removed.</li><li><span id="rfc.iref.d.48"></span> <span id="rfc.iref.c.54"></span>
 (DAV:restore-content-and-dead-properties): The content and dead 
properties of the version-controlled resource are copies of its 
DAV:checked-in version.</li></ul></div><section id="n-example---uncheckout"><h4 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a>&nbsp;<a href="#n-example---uncheckout">Example - UNCHECKOUT</a></h4><div id="rfc.figure.u.45"><p>&gt;&gt;REQUEST</p><pre class="text2">UNCHECKOUT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.46"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Cache-Control: no-cache
</pre></div><div id="rfc.section.4.5.1.p.1"><p>In this example, the 
content and dead properties of the version-controlled resource 
identified by http://www.webdav.org/foo.html are restored to their 
values preceding the most recent CHECKOUT of that version-controlled 
resource.<a class="self" href="#rfc.section.4.5.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_2"><h3 id="rfc.section.4.6"><a href="#rfc.section.4.6">4.6</a>&nbsp;<a href="#n-additional-options-semantics_2">Additional OPTIONS Semantics</a></h3><div id="rfc.section.4.6.p.1"><p>If a server supports the checkout-in-place feature, it <em class="bcp14">MUST</em>
 include "checkout-in-place" as a field in the DAV response header from 
an OPTIONS request on any resource that supports any versioning 
properties, reports, or methods.<a class="self" href="#rfc.section.4.6.p.1">¶</a></p></div></section></section><hr class="noprint"><section id="version-history.feature"><h2 id="rfc.section.5" class="np"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#version-history.feature">Version-History Feature</a></h2><div id="rfc.section.5.p.1"><p>It
 is often useful to have access to a version history even after all 
version-controlled resources for that version history have been deleted.
 A server can provide this functionality by supporting version history 
resources. A version history resource is a resource that exists in a 
server defined namespace and therefore is unaffected by any deletion or 
movement of version-controlled resources. A version history resource is 
an appropriate place to add a property that logically applies to all 
states of a resource. The DAV:expand-property report (see <a href="#REPORT_expand-property" title="DAV:expand-property Report">Section&nbsp;3.8</a>)
 can be applied to the DAV:version-set of a version history resource to 
provide a variety of useful reports on all versions in that version 
history.<a class="self" href="#rfc.section.5.p.1">¶</a></p></div><section id="n-version-history-properties"><h3 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#n-version-history-properties">Version History Properties</a></h3><div id="rfc.section.5.1.p.1"><p>The DAV:resourcetype of a version history <em class="bcp14">MUST</em> be DAV:version-history.<a class="self" href="#rfc.section.5.1.p.1">¶</a></p></div><div id="rfc.section.5.1.p.2"><p>The version-history feature introduces the following <em class="bcp14">REQUIRED</em> properties for a version history.<a class="self" href="#rfc.section.5.1.p.2">¶</a></p></div><section id="PROPERTY_version-set"><h4 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#PROPERTY_version-set">DAV:version-set (protected)</a></h4><div id="rfc.section.5.1.1.p.1"><p>This property identifies each version of this version history. <a class="self" href="#rfc.section.5.1.1.p.1">¶</a></p><span id="rfc.figure.u.47"><pre class="inline">&lt;!ELEMENT version-set (href+)&gt;
</pre></span></div></section><section id="PROPERTY_root-version"><h4 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#PROPERTY_root-version">DAV:root-version (computed)</a></h4><div id="rfc.section.5.1.2.p.1"><p>This property identifies the root version of this version history. <a class="self" href="#rfc.section.5.1.2.p.1">¶</a></p><span id="rfc.figure.u.48"><pre class="inline">&lt;!ELEMENT root-version (href)&gt;
</pre></span></div></section></section><section id="n-additional-version-controlled-resource-properties"><h3 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#n-additional-version-controlled-resource-properties">Additional Version-Controlled Resource Properties</a></h3><div id="rfc.section.5.2.p.1"><p>The version-history feature introduces the following <em class="bcp14">REQUIRED</em> property for a version-controlled resource.<a class="self" href="#rfc.section.5.2.p.1">¶</a></p></div><section id="PROPERTY_version-history"><h4 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a href="#PROPERTY_version-history">DAV:version-history (computed)</a></h4><div id="rfc.section.5.2.1.p.1"><p>This
 property identifies the version history resource for the DAV:checked-in
 or DAV:checked-out version of this version-controlled resource. <a class="self" href="#rfc.section.5.2.1.p.1">¶</a></p><span id="rfc.figure.u.49"><pre class="inline">&lt;!ELEMENT version-history (href)&gt;
</pre></span></div></section></section><section id="n-additional-version-properties_2"><h3 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#n-additional-version-properties_2">Additional Version Properties</a></h3><div id="rfc.section.5.3.p.1"><p>The version-history feature introduces the following <em class="bcp14">REQUIRED</em> property for a version.<a class="self" href="#rfc.section.5.3.p.1">¶</a></p></div><section id="n-dav-version-history--computed-"><h4 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a href="#n-dav-version-history--computed-">DAV:version-history (computed)</a></h4><div id="rfc.section.5.3.1.p.1"><p>This property identifies the version history that contains this version. <a class="self" href="#rfc.section.5.3.1.p.1">¶</a></p><span id="rfc.figure.u.50"><pre class="inline">&lt;!ELEMENT version-history (href)&gt;
</pre></span></div></section></section><section id="REPORT_locate-by-history"><h3 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#REPORT_locate-by-history">DAV:locate-by-history Report</a></h3><div id="rfc.section.5.4.p.1"><p>Many
 properties identify a version from some version history. It is often 
useful to be able to efficiently locate a version-controlled resource 
for that version history. The DAV:locate-by-history report can be 
applied to a collection to locate the collection member that is a 
version-controlled resource for a specified version history resource.<a class="self" href="#rfc.section.5.4.p.1">¶</a></p></div><div id="rfc.section.5.4.p.2"><p><span id="rfc.iref.d.49"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.5.4.p.2">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:locate-by-history XML element. <span id="rfc.figure.u.51"><pre class="inline">&lt;!ELEMENT locate-by-history (version-history-set, prop)&gt;
&lt;!ELEMENT version-history-set (href+)&gt;
prop: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.11" id="rfc.xref.RFC2518.7">Section 12.11</a>
</pre></span> </li><li>The response body for a successful request <em class="bcp14">MUST</em>
 be a DAV:multistatus XML element containing every version-controlled 
resource that is a member of the collection identified by the 
request-URL, and whose DAV:version-history property identifies one of 
the version history resources identified by the request body. The 
DAV:prop element in the request body identifies which properties should 
be reported in the DAV:prop elements in the response body.</li></ul></div><div id="rfc.section.5.4.p.3"><p><span id="rfc.iref.d.50"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.5.4.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.51"></span> <span id="rfc.iref.c.55"></span> (DAV:must-be-version-history): Each member of the DAV:version-history-set element in the request body <em class="bcp14">MUST</em> identify a version history resource.</li></ul></div><section id="n-example---dav-locate-by-history-report"><h4 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a href="#n-example---dav-locate-by-history-report">Example - DAV:locate-by-history Report</a></h4><div id="rfc.figure.u.52"><p>&gt;&gt;REQUEST</p><pre class="text2">REPORT /ws/public HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:locate-by-history xmlns:D="DAV:"&gt;
 &lt;D:version-history-set&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/23&lt;/D:href&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/84&lt;/D:href&gt;
   &lt;D:href&gt;http://repo.webdav.org/his/129&lt;/D:href&gt;
 &lt;D:version-history-set/&gt;
 &lt;D:prop&gt;
   &lt;/D:version-history&gt;
 &lt;/D:prop&gt;
&lt;/D:locate-by-history&gt;
</pre></div><div id="rfc.figure.u.53"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:multistatus xmlns:D="DAV:"&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://www.webdav.org/ws/public/x/test.html&lt;/D:href&gt;
   &lt;D:propstat&gt;
     &lt;D:prop&gt;
       &lt;D:version-history&gt;
         &lt;D:href&gt;http://repo.webdav.org/his/23&lt;/D:href&gt;
       &lt;/D:version-history&gt;
     &lt;/D:prop&gt;
     &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
   &lt;/D:propstat&gt;
 &lt;/D:response&gt;
&lt;/D:multistatus&gt;
</pre></div><div id="rfc.section.5.4.1.p.1"><p>In this example, there is
 only one version-controlled member of /ws/public that is a 
version-controlled resource for one of the three specified version 
history resources. In particular, /ws/public/x/test.html is the 
version-controlled resource for http://repo.webdav.org/his/23.<a class="self" href="#rfc.section.5.4.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_3"><h3 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#n-additional-options-semantics_3">Additional OPTIONS Semantics</a></h3><div id="rfc.section.5.5.p.1"><p>If the server supports the version-history feature, it <em class="bcp14">MUST</em>
 include "version-history" as a field in the DAV response header from an
 OPTIONS request on any resource that supports any versioning 
properties, reports, or methods.<a class="self" href="#rfc.section.5.5.p.1">¶</a></p></div><div id="rfc.section.5.5.p.2"><p>A DAV:version-history-collection-set element <em class="bcp14">MAY</em> be included in the request body to identify collections that may contain version history resources.<a class="self" href="#rfc.section.5.5.p.2">¶</a></p></div><div id="rfc.section.5.5.p.3"><p><span id="rfc.iref.o.1"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.5.5.p.3">¶</a></p><ul class="empty"><li>If an XML request body is included, it <em class="bcp14">MUST</em> be a DAV:options XML element. <span id="rfc.figure.u.54"><pre class="inline">&lt;!ELEMENT options ANY&gt;
ANY value: A sequence of elements with at most one
DAV:version-history-collection-set element.
</pre></span> </li><li>If an XML response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:options-response XML element. <span id="rfc.figure.u.55"><pre class="inline">&lt;!ELEMENT options-response ANY&gt;
ANY value: A sequence of elements with at most one
DAV:version-history-collection-set element.

&lt;!ELEMENT version-history-collection-set (href*)&gt;
</pre></span> </li><li>If DAV:version-history-collection-set is included in the request body, the response body for a successful request <em class="bcp14">MUST</em>
 contain a DAV:version-history-collection-set element identifying 
collections that may contain version histories. An identified collection
 <em class="bcp14">MAY</em> be the root collection of a tree of 
collections, all of which may contain version histories. Since different
 servers can control different parts of the URL namespace, different 
resources on the same host <em class="bcp14">MAY</em> have different DAV:version-history-collection-set values. The identified collections <em class="bcp14">MAY</em> be located on different hosts from the resource.</li></ul></div></section><section id="n-additional-delete-semantics_1"><h3 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a href="#n-additional-delete-semantics_1">Additional DELETE Semantics</a></h3><div id="rfc.section.5.6.p.1"><p><span id="rfc.iref.d.52"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.5.6.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.53"></span> <span id="rfc.iref.c.56"></span> (DAV:delete-version-set): If the request deleted a version history, the request <em class="bcp14">MUST</em> have deleted all versions in the DAV:version-set of that version history, and <em class="bcp14">MUST</em> have satisfied the postconditions for version deletion (see <a href="#additional.delete.semantics" title="Additional DELETE Semantics">Section&nbsp;3.13</a>).</li><li><span id="rfc.iref.d.54"></span> <span id="rfc.iref.c.57"></span> (DAV:version-history-has-root): If the request deleted the root version of a version history, the request <em class="bcp14">MUST</em>
 have updated the DAV:root-version of the version history to refer to 
another version that is an ancestor of all other remaining versions in 
that version history. A result of this postcondition is that every 
version history will have at least one version, and the only way to 
delete all versions is to delete the version history resource.</li></ul></div></section><section id="n-additional-copy-semantics_2"><h3 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a href="#n-additional-copy-semantics_2">Additional COPY Semantics</a></h3><div id="rfc.section.5.7.p.1"><p><span id="rfc.iref.c.58"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.5.7.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.55"></span> <span id="rfc.iref.c.59"></span> (DAV:cannot-copy-history): If the request-URL identifies a version history, the request <em class="bcp14">MUST</em>
 fail. In order to create another version history whose versions have 
the same content and dead properties, the appropriate sequence of 
VERSION-CONTROL, CHECKOUT, PUT, PROPPATCH, and CHECKIN requests must be 
made.</li></ul></div></section><section id="n-additional-move-semantics_2"><h3 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a>&nbsp;<a href="#n-additional-move-semantics_2">Additional MOVE Semantics</a></h3><div id="rfc.section.5.8.p.1"><p><span id="rfc.iref.m.4"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.5.8.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.56"></span> <span id="rfc.iref.c.60"></span> (DAV:cannot-rename-history): If the request-URL identifies a version history, the request <em class="bcp14">MUST</em> fail.</li></ul></div></section><section id="n-additional-version-control-semantics_1"><h3 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a>&nbsp;<a href="#n-additional-version-control-semantics_1">Additional VERSION-CONTROL Semantics</a></h3><div id="rfc.section.5.9.p.1"><p><span id="rfc.iref.v.9"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.5.9.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.57"></span> <span id="rfc.iref.c.61"></span> (DAV:new-version-history): If the request created a new version history, the request <em class="bcp14">MUST</em> have allocated a new server-defined URL for that version history that <em class="bcp14">MUST NOT</em> have previously identified any other resource, and <em class="bcp14">MUST NOT</em> ever identify a resource other than this version history.</li></ul></div></section><section id="n-additional-checkin-semantics_1"><h3 id="rfc.section.5.10"><a href="#rfc.section.5.10">5.10</a>&nbsp;<a href="#n-additional-checkin-semantics_1">Additional CHECKIN Semantics</a></h3><div id="rfc.section.5.10.p.1"><p><span id="rfc.iref.c.62"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.5.10.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.58"></span> <span id="rfc.iref.c.63"></span> (DAV:add-to-history): A URL for the new version resource <em class="bcp14">MUST</em> have been added to the DAV:version-set of the version history of the DAV:checked-out version.</li></ul></div></section></section><hr class="noprint"><section id="workspace.feature"><h2 id="rfc.section.6" class="np"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#workspace.feature">Workspace Feature</a></h2><div id="rfc.section.6.p.1"><p>In
 order to allow multiple users to work concurrently on adding versions 
to the same version history, it is necessary to allocate on the server 
multiple checked-out resources for the same version history. Even if 
only one user is making changes to a resource, that user will sometimes 
wish to create a "private" version, and then to expose that version at a
 later time. One way to provide this functionality depends on the client
 keeping track of its current set of checked-out resources. This is the 
working-resource feature defined in <a href="#label.feature" title="Label Feature">Section&nbsp;8</a>.
 The other way to provide this functionality avoids the need for 
persistent state on the client, and instead has the server maintain a 
human meaningful namespace for related sets of checked-out resources. 
This is the workspace feature defined in this section.<a class="self" href="#rfc.section.6.p.1">¶</a></p></div><div id="rfc.section.6.p.2"><p>The
 workspace feature introduces a "workspace resource". A workspace 
resource is a collection whose members are related version-controlled 
and non-version-controlled resources. Multiple workspaces may be used to
 expose different versions and configurations of a set of 
version-controlled resources concurrently. In order to make changes to a
 version-controlled resource in one workspace visible in another 
workspace, that version-controlled resource must be checked in, and then
 the corresponding version-controlled resource in the other workspace 
can be updated to display the content and dead properties of the new 
version.<a class="self" href="#rfc.section.6.p.2">¶</a></p></div><div id="rfc.section.6.p.3"><p>In order to ensure unambiguous merging (see <a href="#merge.feature" title="Merge Feature">Section&nbsp;11</a>) and baselining (see <a href="#baseline.feature" title="Baseline Feature">Section&nbsp;12</a>)
 semantics, a workspace may contain at most one version-controlled 
resource for a given version history. This is required for unambiguous 
merging because the MERGE method must identify which version-controlled 
resource is to be the merge target of a given version. This is required 
for unambiguous baselining because a baseline can only select one 
version for a given version-controlled resource.<a class="self" href="#rfc.section.6.p.3">¶</a></p></div><div id="rfc.section.6.p.4"><p>Initially,
 an empty workspace can be created. Non-version-controlled resources can
 then be added to the workspace with standard WebDAV requests such as 
PUT and MKCOL. Version-controlled resources can be added to the 
workspace with VERSION-CONTROL requests. If the baseline feature is 
supported, collections in the workspace can be placed under baseline 
control, and then initialized by existing baselines.<a class="self" href="#rfc.section.6.p.4">¶</a></p></div><section id="n-workspace-properties"><h3 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#n-workspace-properties">Workspace Properties</a></h3><div id="rfc.section.6.1.p.1"><p>The workspace feature introduces the following <em class="bcp14">REQUIRED</em> property for a workspace.<a class="self" href="#rfc.section.6.1.p.1">¶</a></p></div><section id="PROPERTY_workspace-checkout-set"><h4 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a href="#PROPERTY_workspace-checkout-set">DAV:workspace-checkout-set (computed)</a></h4><div id="rfc.section.6.1.1.p.1"><p>This property identifies each checked-out resource whose DAV:workspace property identifies this workspace. <a class="self" href="#rfc.section.6.1.1.p.1">¶</a></p><span id="rfc.figure.u.56"><pre class="inline">&lt;!ELEMENT workspace-checkout-set (href*)&gt;
</pre></span></div></section></section><section id="n-additional-resource-properties_2"><h3 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#n-additional-resource-properties_2">Additional Resource Properties</a></h3><div id="rfc.section.6.2.p.1"><p>The workspace feature introduces the following <em class="bcp14">REQUIRED</em> property for a WebDAV resource.<a class="self" href="#rfc.section.6.2.p.1">¶</a></p></div><section id="PROPERTY_workspace"><h4 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a href="#PROPERTY_workspace">DAV:workspace (protected)</a></h4><div id="rfc.section.6.2.1.p.1"><p>The DAV:workspace property of a workspace resource <em class="bcp14">MUST</em> identify itself. The DAV:workspace property of any other type of resource <em class="bcp14">MUST</em> be the same as the DAV:workspace of its parent collection. <a class="self" href="#rfc.section.6.2.1.p.1">¶</a></p><span id="rfc.figure.u.57"><pre class="inline">&lt;!ELEMENT workspace (href)&gt;
</pre></span></div></section></section><section id="METHOD_MKWORKSPACE"><h3 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#METHOD_MKWORKSPACE">MKWORKSPACE Method</a></h3><div id="rfc.section.6.3.p.1"><p>A MKWORKSPACE request creates a new workspace resource. A server <em class="bcp14">MAY</em>
 restrict workspace creation to particular collections, but a client can
 determine the location of these collections from a 
DAV:workspace-collection-set OPTIONS request (see <a href="#additional.options.semantics.with.workspace.feature" title="Additional OPTIONS Semantics">Section&nbsp;6.4</a>).<a class="self" href="#rfc.section.6.3.p.1">¶</a></p></div><div id="rfc.section.6.3.p.2"><p>If a MKWORKSPACE request fails, the server state preceding the request <em class="bcp14">MUST</em> be restored.<a class="self" href="#rfc.section.6.3.p.2">¶</a></p></div><div id="rfc.section.6.3.p.3"><p><span id="rfc.iref.m.5"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.6.3.p.3">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:mkworkspace XML element. <span id="rfc.figure.u.58"><pre class="inline">&lt;!ELEMENT mkworkspace ANY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:mkworkspace-response XML element. <span id="rfc.figure.u.59"><pre class="inline">&lt;!ELEMENT mkworkspace-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.6.3.p.4"><p><span id="rfc.iref.m.6"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.6.3.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.59"></span> <span id="rfc.iref.c.64"></span> (DAV:resource-must-be-null): A resource <em class="bcp14">MUST NOT</em> exist at the request-URL.</li><li><span id="rfc.iref.d.60"></span> <span id="rfc.iref.c.65"></span> (DAV:workspace-location-ok): The request-URL <em class="bcp14">MUST</em> identify a location where a workspace can be created.</li></ul></div><div id="rfc.section.6.3.p.5"><p><span id="rfc.iref.m.7"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.6.3.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.61"></span> <span id="rfc.iref.c.66"></span> (DAV:initialize-workspace): A new workspace exists at the request-URL. The DAV:resourcetype of the workspace <em class="bcp14">MUST</em> be DAV:collection. The DAV:workspace of the workspace <em class="bcp14">MUST</em> identify the workspace.</li></ul></div><section id="n-example---mkworkspace"><h4 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#n-example---mkworkspace">Example - MKWORKSPACE</a></h4><div id="rfc.figure.u.60"><p>&gt;&gt;REQUEST</p><pre class="text2">MKWORKSPACE /ws/public HTTP/1.1
Host: www.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.61"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Cache-Control: no-cache
</pre></div><div id="rfc.section.6.3.1.p.1"><p>In this example, a new workspace is created at http://www.webdav.org/ws/public.<a class="self" href="#rfc.section.6.3.1.p.1">¶</a></p></div></section></section><section id="additional.options.semantics.with.workspace.feature"><h3 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#additional.options.semantics.with.workspace.feature">Additional OPTIONS Semantics</a></h3><div id="rfc.section.6.4.p.1"><p>If a server supports the workspace feature, it <em class="bcp14">MUST</em>
 include "workspace" as a field in the DAV response header from an 
OPTIONS request on any resource that supports any versioning properties,
 reports, or methods.<a class="self" href="#rfc.section.6.4.p.1">¶</a></p></div><div id="rfc.section.6.4.p.2"><p>If a server supports the workspace feature, it <em class="bcp14">MUST</em> also support the checkout-in-place feature and the version-history feature.<a class="self" href="#rfc.section.6.4.p.2">¶</a></p></div><div id="rfc.section.6.4.p.3"><p>A DAV:workspace-collection-set element <em class="bcp14">MAY</em> be included in the request body to identify collections that may contain workspace resources.<a class="self" href="#rfc.section.6.4.p.3">¶</a></p></div><div id="rfc.section.6.4.p.4"><p><span id="rfc.iref.o.2"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.6.4.p.4">¶</a></p><ul class="empty"><li>If an XML request body is included, it <em class="bcp14">MUST</em> be a DAV:options XML element. <span id="rfc.figure.u.62"><pre class="inline">&lt;!ELEMENT options ANY&gt;
ANY value: A sequence of elements with at most one
DAV:workspace-collection-set element.
</pre></span> </li><li>If an XML response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:options-response XML element. <span id="rfc.figure.u.63"><pre class="inline">&lt;!ELEMENT options-response ANY&gt;
ANY value: A sequence of elements with at most one
DAV:workspace-collection-set element.

&lt;!ELEMENT workspace-collection-set (href*)&gt;
</pre></span> </li><li>If DAV:workspace-collection-set is included in the request body, the response body for a successful request <em class="bcp14">MUST</em> contain a DAV:workspace-collection-set element identifying collections that may contain workspaces. An identified collection <em class="bcp14">MAY</em>
 be the root collection of a tree of collections, all of which may 
contain workspaces. Since different servers can control different parts 
of the URL namespace, different resources on the same host <em class="bcp14">MAY</em> have different DAV:workspace-collection-set values. The identified collections <em class="bcp14">MAY</em> be located on different hosts from the resource.</li></ul></div><section id="n-example---options"><h4 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a href="#n-example---options">Example - OPTIONS</a></h4><div id="rfc.figure.u.64"><p>&gt;&gt;REQUEST</p><pre class="text2">OPTIONS /doc HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:options xmlns:D="DAV:"&gt;
  &lt;D:version-history-collection-set/&gt;
  &lt;D:workspace-collection-set/&gt;
&lt;/D:options&gt;
</pre></div><div id="rfc.figure.u.65"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
DAV: 1
DAV: version-control,checkout-in-place,version-history,workspace
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:options-response xmlns:D="DAV:"&gt;
  &lt;D:version-history-collection-set&gt;
    &lt;D:href&gt;http://repo.webdav.org/his&lt;/D:href&gt;
  &lt;/D:version-history-collection-set&gt;
  &lt;D:workspace-collection-set&gt;
    &lt;D:href&gt;http://www.webdav.org/public/ws&lt;/D:href&gt;
    &lt;D:href&gt;http://www.webdav.org/private/ws&lt;/D:href&gt;
  &lt;/D:workspace-collection-set&gt;
&lt;/D:options-response&gt;
</pre></div><div id="rfc.section.6.4.1.p.1"><p>In this example, the 
server indicates that it provides Class 1 DAV support and 
basic-server-workspace versioning support. In addition, the server 
indicates the requested locations of the version history resources and 
the workspace resources.<a class="self" href="#rfc.section.6.4.1.p.1">¶</a></p></div></section></section><section id="n-additional-delete-semantics_2"><h3 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#n-additional-delete-semantics_2">Additional DELETE Semantics</a></h3><div id="rfc.section.6.5.p.1"><p><span id="rfc.iref.d.62"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.6.5.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.63"></span> <span id="rfc.iref.c.67"></span>
 (DAV:delete-workspace-members): If a workspace is deleted, any resource
 that identifies that workspace in its DAV:workspace property <em class="bcp14">MUST</em> be deleted.</li></ul></div></section><section id="n-additional-move-semantics_3"><h3 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#n-additional-move-semantics_3">Additional MOVE Semantics</a></h3><div id="rfc.section.6.6.p.1"><p><span id="rfc.iref.m.8"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.6.6.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.64"></span> <span id="rfc.iref.c.68"></span> (DAV:workspace-member-moved): If the request-URL did not identify a workspace, the DAV:workspace of the destination <em class="bcp14">MUST</em> have been updated to have the same value as the DAV:workspace of the parent collection of the destination.</li><li><span id="rfc.iref.d.65"></span> <span id="rfc.iref.c.69"></span> (DAV:workspace-moved): If the request-URL identified a workspace, any reference to that workspace in a DAV:workspace property <em class="bcp14">MUST</em> have been updated to refer to the new location of that workspace.</li></ul></div></section><section id="n-additional-version-control-semantics_2"><h3 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a href="#n-additional-version-control-semantics_2">Additional VERSION-CONTROL Semantics</a></h3><div id="rfc.section.6.7.p.1"><p>A
 VERSION-CONTROL request can be used to create a new version-controlled 
resource for an existing version history. This allows the creation of 
version-controlled resources for the same version history in multiple 
workspaces.<a class="self" href="#rfc.section.6.7.p.1">¶</a></p></div><div id="rfc.section.6.7.p.2"><p><span id="rfc.iref.v.10"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.6.7.p.2">¶</a></p><ul class="empty"><li><span id="rfc.figure.u.66"><pre class="inline">&lt;!ELEMENT version-control ANY&gt;
ANY value: A sequence of elements with at most one DAV:version
element.

&lt;!ELEMENT version (href)&gt;
</pre></span> </li></ul></div><div id="rfc.section.6.7.p.3"><p><span id="rfc.iref.v.11"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.6.7.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.66"></span> <span id="rfc.iref.c.70"></span>
 (DAV:cannot-add-to-existing-history): If the DAV:version-control 
request body element contains a DAV:version element, the request-URL <em class="bcp14">MUST NOT</em> identify a resource.</li><li><span id="rfc.iref.d.67"></span> <span id="rfc.iref.c.71"></span> (DAV:must-be-version): The DAV:href of the DAV:version element <em class="bcp14">MUST</em> identify a version.</li><li><span id="rfc.iref.d.68"></span> <span id="rfc.iref.c.72"></span>
 (DAV:one-version-controlled-resource-per-history-per-workspace): If the
 DAV:version-control request body specifies a version, and if the 
request-URL is a member of a workspace, then there <em class="bcp14">MUST NOT</em>
 already be a version-controlled member of that workspace whose 
DAV:checked-in or DAV:checked-out property identifies any version from 
the version history of the version specified in the request body.</li></ul></div><div id="rfc.section.6.7.p.4"><p><span id="rfc.iref.v.12"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.6.7.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.69"></span> <span id="rfc.iref.c.73"></span>
 (DAV:new-version-controlled-resource): If the request-URL did NOT 
identify a resource, a new version-controlled resource exists at the 
request-URL whose content and dead properties are initialized by those 
of the version in the request body, and whose DAV:checked-in property 
identifies that version.</li></ul></div><section id="n-example---version-control--using-an-existing-version-history-"><h4 id="rfc.section.6.7.1"><a href="#rfc.section.6.7.1">6.7.1</a>&nbsp;<a href="#n-example---version-control--using-an-existing-version-history-">Example - VERSION-CONTROL (using an existing version history)</a></h4><div id="rfc.figure.u.67"><p>&gt;&gt;REQUEST</p><pre class="text2">VERSION-CONTROL /ws/public/bar.html HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:version-control xmlns:D="DAV:"&gt;
  &lt;D:version&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/12/ver/V3&lt;/D:href&gt;
  &lt;/D:version&gt;
&lt;/D:version-control&gt;
</pre></div><div id="rfc.figure.u.68"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Cache-Control: no-cache
</pre></div><div id="rfc.section.6.7.1.p.1"><p>In this example, a new 
version-controlled resource is created at /ws/public/bar.html. The 
content and dead properties of the new version-controlled resource are 
initialized to be the same as those of the version identified by 
http://repo.webdav.org/his/12/ver/V3.<a class="self" href="#rfc.section.6.7.1.p.1">¶</a></p></div></section></section></section><hr class="noprint"><section id="n-update-feature"><h2 id="rfc.section.7" class="np"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#n-update-feature">UPDATE Feature</a></h2><div id="rfc.section.7.p.1"><p>The
 update feature provides a mechanism for changing the state of a 
checked-in version-controlled resource to be that of another version 
from the version history of that resource.<a class="self" href="#rfc.section.7.p.1">¶</a></p></div><section id="METHOD_UPDATE"><h3 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#METHOD_UPDATE">UPDATE Method</a></h3><div id="rfc.section.7.1.p.1"><p>The
 UPDATE method modifies the content and dead properties of a checked-in 
version-controlled resource (the "update target") to be those of a 
specified version (the "update source") from the version history of that
 version-controlled resource.<a class="self" href="#rfc.section.7.1.p.1">¶</a></p></div><div id="rfc.section.7.1.p.2"><p>The
 response to an UPDATE request identifies the resources modified by the 
request, so that a client can efficiently update any cached state it is 
maintaining. Extensions to the UPDATE method allow multiple resources to
 be modified from a single UPDATE request (see <a href="#additional.update.semantics.with.baseline.feature" title="Additional UPDATE Semantics">Section&nbsp;12.13</a>).<a class="self" href="#rfc.section.7.1.p.2">¶</a></p></div><div id="rfc.section.7.1.p.3"><p><span id="rfc.iref.u.6"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.7.1.p.3">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:update element. <span id="rfc.figure.u.69"><pre class="inline">&lt;!ELEMENT update ANY&gt;
ANY value: A sequence of elements with at most one DAV:version
element and at most one DAV:prop element.
&lt;!ELEMENT version (href)&gt;
prop: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.11" id="rfc.xref.RFC2518.8">Section 12.11</a>
</pre></span> </li><li>The response for a successful request <em class="bcp14">MUST</em>
 be a 207 Multi-Status, where the DAV:multistatus XML element in the 
response body identifies all resources that have been modified by the 
request. <span id="rfc.figure.u.70"><pre class="inline">multistatus: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.9" id="rfc.xref.RFC2518.9">Section 12.9</a>
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.7.1.p.4"><p><span id="rfc.iref.u.7"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.7.1.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.70"></span> <span id="rfc.iref.c.74"></span>
 (DAV:update-content-and-properties): If the DAV:version element in the 
request body identified a version that is in the same version history as
 the DAV:checked-in version of a version-controlled resource identified 
by the request-URL, then the content and dead properties of that 
version-controlled resource <em class="bcp14">MUST</em> be the same as 
those of the version specified by the DAV:version element, and the 
DAV:checked-in property of the version-controlled resource <em class="bcp14">MUST</em> identify that version. The request-URL <em class="bcp14">MUST</em> appear in a DAV:response element in the response body.</li><li><span id="rfc.iref.d.71"></span> <span id="rfc.iref.c.75"></span> (DAV:report-properties): If DAV:prop is specified in the request body, the properties specified in the DAV:prop element <em class="bcp14">MUST</em> be reported in the DAV:response elements in the response body.</li></ul></div><section id="n-example---update"><h4 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a href="#n-example---update">Example - UPDATE</a></h4><div id="rfc.figure.u.71"><p>&gt;&gt;REQUEST</p><pre class="text2">UPDATE /foo.html HTTP/1.1
Host: www.webdav.org
Content-type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:update xmlns:D="DAV:"&gt;
  &lt;D:version&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/23/ver/33&lt;/D:href&gt;
  &lt;/D:version&gt;
&lt;/D:update&gt;
</pre></div><div id="rfc.figure.u.72"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx
Cache-Control: no-cache

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:multistatus xmlns:D="DAV:"&gt;
 &lt;D:response&gt;
   &lt;D:href&gt;http://www.webdav.org/foo.html&lt;/D:href&gt;
   &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
  &lt;/D:response&gt;
</pre></div><div id="rfc.section.7.1.1.p.1"><p>In this example, the 
content and dead properties of http://repo.webdav.org/his/23/ver/33 are 
copied to the version-controlled resource /foo.html, and the 
DAV:checked-in property of /foo.html is updated to refer to 
http://repo.webdav.org/his/23/ver/33.<a class="self" href="#rfc.section.7.1.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_4"><h3 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#n-additional-options-semantics_4">Additional OPTIONS Semantics</a></h3><div id="rfc.section.7.2.p.1"><p>If the server supports the update feature, it <em class="bcp14">MUST</em>
 include "update" as a field in the DAV response header from an OPTIONS 
request on any resource that supports any versioning properties, 
reports, or methods.<a class="self" href="#rfc.section.7.2.p.1">¶</a></p></div></section></section><hr class="noprint"><section id="label.feature"><h2 id="rfc.section.8" class="np"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#label.feature">Label Feature</a></h2><div id="rfc.section.8.p.1"><p>A
 version "label" is a string that distinguishes one version in a version
 history from all other versions in that version history. A label can 
automatically be assigned by a server, or it can be assigned by a client
 in order to provide a meaningful name for that version. A given version
 label can be assigned to at most one version of a given version 
history, but client assigned labels can be reassigned to another version
 at any time. Note that although a given label can be applied to at most
 one version from the same version history, the same label can be 
applied to versions from different version histories.<a class="self" href="#rfc.section.8.p.1">¶</a></p></div><div id="rfc.section.8.p.2"><p>For
 certain methods, if the request-URL identifies a version-controlled 
resource, a label can be specified in a Label request header (see <a href="#label.header" title="Label Header">Section&nbsp;8.3</a>)
 to cause the method to be applied to the version selected by that label
 from the version history of that version-controlled resource.<a class="self" href="#rfc.section.8.p.2">¶</a></p></div><section id="n-additional-version-properties_3"><h3 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#n-additional-version-properties_3">Additional Version Properties</a></h3><div id="rfc.section.8.1.p.1"><p>The label feature introduces the following <em class="bcp14">REQUIRED</em> property for a version.<a class="self" href="#rfc.section.8.1.p.1">¶</a></p></div><section id="PROPERTY_label-name-set"><h4 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a href="#PROPERTY_label-name-set">DAV:label-name-set (protected)</a></h4><div id="rfc.section.8.1.1.p.1"><p>This property contains the labels that currently select this version. <a class="self" href="#rfc.section.8.1.1.p.1">¶</a></p><span id="rfc.figure.u.73"><pre class="inline">&lt;!ELEMENT label-name-set (label-name*)&gt;
&lt;!ELEMENT label-name (#PCDATA)&gt;
PCDATA value: string
</pre></span></div></section></section><section id="METHOD_LABEL"><h3 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#METHOD_LABEL">LABEL Method</a></h3><div id="rfc.section.8.2.p.1"><p>A LABEL request can be applied to a version to modify the labels that select that version. The case of a label name <em class="bcp14">MUST</em> be preserved when it is stored and retrieved. When comparing two label names to decide if they match or not, a server <em class="bcp14">SHOULD</em> use a case-sensitive URL-escaped UTF-8 encoded comparison of the two label names.<a class="self" href="#rfc.section.8.2.p.1">¶</a></p></div><div id="rfc.section.8.2.p.2"><p>If a LABEL request is applied to a checked in version-controlled resource, the operation <em class="bcp14">MUST</em> be applied to the DAV:checked-in version of that version-controlled resource.<a class="self" href="#rfc.section.8.2.p.2">¶</a></p></div><div id="rfc.section.8.2.p.3"><p><span id="rfc.iref.l.2"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.8.2.p.3">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:label element. <span id="rfc.figure.u.74"><pre class="inline">&lt;!ELEMENT label ANY&gt;
ANY value: A sequence of elements with at most one DAV:add,
DAV:set, or DAV:remove element.

&lt;!ELEMENT add (label-name)&gt;
&lt;!ELEMENT set (label-name)&gt;
&lt;!ELEMENT remove (label-name)&gt;
&lt;!ELEMENT label-name (#PCDATA)&gt;
PCDATA value: string
</pre></span> </li><li>The request <em class="bcp14">MAY</em> include a Label header.</li><li>The request <em class="bcp14">MAY</em>
 include a Depth header. If no Depth header is included, Depth:0 is 
assumed. Standard depth semantics apply, and the request is applied to 
the collection identified by the request-URL and to all members of the 
collection that satisfy the Depth value. If a Depth header is included 
and the request fails on any resource, the response <em class="bcp14">MUST</em> be a 207 Multi-Status that identifies all resources for which the request has failed.</li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:label-response XML element. <span id="rfc.figure.u.75"><pre class="inline">&lt;!ELEMENT label-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.8.2.p.4"><p><span id="rfc.iref.l.3"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.8.2.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.72"></span> <span id="rfc.iref.c.76"></span> (DAV:must-be-checked-in): If the request-URL identifies a version-controlled resource, the version-controlled resource <em class="bcp14">MUST</em> be checked in.</li><li><span id="rfc.iref.d.73"></span> <span id="rfc.iref.c.77"></span>
 (DAV:must-select-version-in-history): If a Label request header is 
included and the request-URL identifies a version-controlled resource, 
the specified label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource.</li><li><span id="rfc.iref.d.74"></span> <span id="rfc.iref.c.78"></span> (DAV:add-must-be-new-label): If DAV:add is specified in the request body, the specified label <em class="bcp14">MUST NOT</em> appear in the DAV:label-name-set of any version in the version history of that version-controlled resource.</li><li><span id="rfc.iref.d.75"></span> <span id="rfc.iref.c.79"></span> (DAV:label-must-exist): If DAV:remove is specified in the request body, the specified label <em class="bcp14">MUST</em> appear in the DAV:label-name-set of that version.</li></ul></div><div id="rfc.section.8.2.p.5"><p><span id="rfc.iref.l.4"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.8.2.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.76"></span> <span id="rfc.iref.c.80"></span> (DAV:add-or-set-label): If DAV:add or DAV:set is specified in the request body, the specified label <em class="bcp14">MUST</em> appear in the DAV:label-name-set of the specified version, and <em class="bcp14">MUST NOT</em> appear in the DAV:label-name-set of any other version in the version history of that version.</li><li><span id="rfc.iref.d.77"></span> <span id="rfc.iref.c.81"></span> (DAV:remove-label): If DAV:remove is specified in the request body, the specified label <em class="bcp14">MUST NOT</em> appear in the DAV:label-name-set of any version in the version history of that version.</li></ul></div><section id="n-example---setting-a-label"><h4 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a href="#n-example---setting-a-label">Example - Setting a label</a></h4><div id="rfc.figure.u.76"><p>&gt;&gt;REQUEST</p><pre class="text2">LABEL /foo.html HTTP/1.1
Host: www.webdav.org
Content-type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:label xmlns:D="DAV:"&gt;
  &lt;D:set&gt;
    &lt;D:label-name&gt;default&lt;/D:label-name&gt;
  &lt;/D:set&gt;
&lt;/D:label&gt;
</pre></div><div id="rfc.figure.u.77"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Cache-Control: no-cache
</pre></div><div id="rfc.section.8.2.1.p.1"><p>In this example, the label "default" is applied to the DAV:checked-in version of /foo.html.<a class="self" href="#rfc.section.8.2.1.p.1">¶</a></p></div></section></section><section id="label.header"><h3 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#label.header">Label Header</a></h3><div id="rfc.section.8.3.p.1"><p>For
 certain methods (e.g. GET, PROPFIND), if the request-URL identifies a 
version-controlled resource, a label can be specified in a Label request
 header to cause the method to be applied to the version selected by 
that label from the version history of that version-controlled resource.<a class="self" href="#rfc.section.8.3.p.1">¶</a></p></div><div id="rfc.section.8.3.p.2" class="avoidbreakafter"><p>The
 value of a label header is the name of a label, encoded using 
URL-escaped UTF-8. For example, the label "release B.3" is identified by
 the following header:<a class="self" href="#rfc.section.8.3.p.2">¶</a></p></div><div id="rfc.figure.u.78"><pre class="text">Label: release%20B.3
</pre></div><div id="rfc.section.8.3.p.3"><p>A Label header <em class="bcp14">MUST</em> have no effect on a request whose request-URL does not identify a version-controlled resource. In particular, it <em class="bcp14">MUST</em> have no effect on a request whose request-URL identifies a version or a version history.<a class="self" href="#rfc.section.8.3.p.3">¶</a></p></div><div id="rfc.section.8.3.p.4"><p>A server <em class="bcp14">MUST</em>
 return an HTTP-1.1 Vary header containing Label in a successful 
response to a cacheable request (e.g., GET) that includes a Label 
header.<a class="self" href="#rfc.section.8.3.p.4">¶</a></p></div></section><section id="n-additional-options-semantics_5"><h3 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#n-additional-options-semantics_5">Additional OPTIONS Semantics</a></h3><div id="rfc.section.8.4.p.1"><p>If the server supports the label feature, it <em class="bcp14">MUST</em>
 include "label" as a field in the DAV response header from an OPTIONS 
request on any resource that supports any versioning properties, 
reports, or methods.<a class="self" href="#rfc.section.8.4.p.1">¶</a></p></div></section><section id="n-additional-get-semantics"><h3 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a href="#n-additional-get-semantics">Additional GET Semantics</a></h3><div id="rfc.section.8.5.p.1"><p><span id="rfc.iref.g.1"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.8.5.p.1">¶</a></p><ul class="empty"><li>The request <em class="bcp14">MAY</em> include a Label header.</li></ul></div><div id="rfc.section.8.5.p.2"><p><span id="rfc.iref.g.2"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.8.5.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.78"></span> <span id="rfc.iref.c.82"></span>
 (DAV:must-select-version-in-history): If a Label request header is 
included and the request-URL identifies a version-controlled resource, 
the specified label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource.</li></ul></div><div id="rfc.section.8.5.p.3"><p><span id="rfc.iref.g.3"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.8.5.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.79"></span> <span id="rfc.iref.c.83"></span>
 (DAV:apply-request-to-labeled-version): If the request-URL identifies a
 version-controlled resource and a Label request header is included, the
 response <em class="bcp14">MUST</em> contain the content of the specified version rather than that of the version-controlled resource.</li></ul></div></section><section id="n-additional-propfind-semantics_2"><h3 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a href="#n-additional-propfind-semantics_2">Additional PROPFIND Semantics</a></h3><div id="rfc.section.8.6.p.1"><p><span id="rfc.iref.p.7"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.8.6.p.1">¶</a></p><ul class="empty"><li>The request <em class="bcp14">MAY</em> include a Label header.</li></ul></div><div id="rfc.section.8.6.p.2"><p><span id="rfc.iref.p.8"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.8.6.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.80"></span> <span id="rfc.iref.c.84"></span>
 (DAV:must-select-version-in-history): If a Label request header is 
included and the request-URL identifies a version-controlled resource, 
the specified label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource.</li></ul></div><div id="rfc.section.8.6.p.3"><p><span id="rfc.iref.p.9"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.8.6.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.81"></span> <span id="rfc.iref.c.85"></span>
 (DAV:apply-request-to-labeled-version): If the request-URL identifies a
 version-controlled resource and a Label request header is included, the
 response <em class="bcp14">MUST</em> contain the properties of the specified version rather than that of the version-controlled resource.</li></ul></div></section><section id="n-additional-copy-semantics_3"><h3 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a href="#n-additional-copy-semantics_3">Additional COPY Semantics</a></h3><div id="rfc.section.8.7.p.1"><p><span id="rfc.iref.c.86"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.8.7.p.1">¶</a></p><ul class="empty"><li>The request <em class="bcp14">MAY</em> include a Label header.</li></ul></div><div id="rfc.section.8.7.p.2"><p><span id="rfc.iref.c.87"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.8.7.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.82"></span> <span id="rfc.iref.c.88"></span>
 (DAV:must-select-version-in-history): If a Label request header is 
included and the request-URL identifies a version-controlled resource, 
the specified label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource.</li></ul></div><div id="rfc.section.8.7.p.3"><p><span id="rfc.iref.c.89"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.8.7.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.83"></span> <span id="rfc.iref.c.90"></span>
 (DAV:apply-request-to-labeled-version): If the request-URL identifies a
 version-controlled resource and a Label request header is included, the
 request <em class="bcp14">MUST</em> have copied the properties and content of the specified version rather than that of the version-controlled resource.</li></ul></div></section><section id="n-additional-checkout-semantics_1"><h3 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a href="#n-additional-checkout-semantics_1">Additional CHECKOUT Semantics</a></h3><div id="rfc.section.8.8.p.1"><p>If
 the server supports the working-resource option, a LABEL header may be 
included to check out the version selected by the specified label.<a class="self" href="#rfc.section.8.8.p.1">¶</a></p></div><div id="rfc.section.8.8.p.2"><p><span id="rfc.iref.c.91"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.8.8.p.2">¶</a></p><ul class="empty"><li>The request <em class="bcp14">MAY</em> include a Label header.</li></ul></div><div id="rfc.section.8.8.p.3"><p><span id="rfc.iref.c.92"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.8.8.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.84"></span> <span id="rfc.iref.c.93"></span>
 (DAV:must-select-version-in-history): If a Label request header is 
included and the request-URL identifies a version-controlled resource, 
the specified label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource.</li><li><span id="rfc.iref.d.85"></span> <span id="rfc.iref.c.94"></span> (DAV:must-not-have-label-and-apply-to-version): If a Label request header is included, the request body <em class="bcp14">MUST NOT</em> contain a DAV:apply-to-version element.</li></ul></div><div id="rfc.section.8.8.p.4"><p><span id="rfc.iref.c.95"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.8.8.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.86"></span> <span id="rfc.iref.c.96"></span>
 (DAV:apply-request-to-labeled-version): If the request-URL identifies a
 checked-in version-controlled resource, and a Label request header is 
included, the CHECKOUT <em class="bcp14">MUST</em> have been applied to the version selected by the specified label, and not to the version-controlled resource itself.</li></ul></div></section><section id="n-additional-update-semantics"><h3 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a href="#n-additional-update-semantics">Additional UPDATE Semantics</a></h3><div id="rfc.section.8.9.p.1"><p>If
 the request body of an UPDATE request contains a DAV:label-name 
element, the update target is the resource identified by the 
request-URL, and the update source is the version selected by the 
specified label from the version history of the update target.<a class="self" href="#rfc.section.8.9.p.1">¶</a></p></div><div id="rfc.section.8.9.p.2"><p><span id="rfc.iref.u.8"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.8.9.p.2">¶</a></p><ul class="empty"><li><span id="rfc.figure.u.79"><pre class="inline">&lt;!ELEMENT update ANY&gt;
ANY value: A sequence of elements with at most one DAV:label-name
or DAV:version element (but not both).
&lt;!ELEMENT label-name (#PCDATA)&gt;
PCDATA value: string
</pre></span> The request <em class="bcp14">MAY</em> include a Depth 
header. If no Depth header is included, Depth:0 is assumed. Standard 
depth semantics apply, and the request is applied to the collection 
identified by the request-URL and to all members of the collection that 
satisfy the Depth value. If a Depth header is included and the request 
fails on any resource, the response <em class="bcp14">MUST</em> be a 207 Multi-Status that identifies all resources for which the request has failed.</li></ul></div><div id="rfc.section.8.9.p.3"><p><span id="rfc.iref.u.9"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.8.9.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.87"></span> <span id="rfc.iref.c.97"></span> (DAV:must-select-version-in-history): If the request includes a DAV:label-name element in the request body, the label <em class="bcp14">MUST</em> select a version in the version history of the version-controlled resource identified by the request-URL.</li><li><span id="rfc.iref.d.88"></span> <span id="rfc.iref.c.98"></span>
 (DAV:depth-update): If the request includes a Depth header, standard 
depth semantics apply, and the request is applied to the collection 
identified by the request-URL and to all members of the collection that 
satisfy the Depth value. The request <em class="bcp14">MUST</em> be 
applied to a collection before being applied to any members of that 
collection, since an update of a version-controlled collection might 
change the membership of that collection.</li></ul></div><div id="rfc.section.8.9.p.4"><p><span id="rfc.iref.u.10"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.8.9.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.89"></span> <span id="rfc.iref.c.99"></span>
 (DAV:apply-request-to-labeled-version): If a DAV:label-name element 
appears in the request body, the content and dead properties of the 
version-controlled resource must have been updated to be those of the 
version selected by that label.</li></ul></div></section></section><hr class="noprint"><section id="n-working-resource-feature"><h2 id="rfc.section.9" class="np"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#n-working-resource-feature">Working-Resource Feature</a></h2><div id="rfc.section.9.p.1"><p>The
 working-resource feature provides an alternative to the workspace 
feature for supporting parallel development. Unlike the workspace 
feature, where the desired configuration of versions and checked-out 
resources is maintained on the server, the working-resource feature 
maintains the configuration on the client. This simplifies the server 
implementation, but does not allow a user to access the configuration 
from clients in different physical locations, such as from another 
office, from home, or while traveling. Another difference is that the 
workspace feature isolates clients from a logical change that involves 
renaming shared resources, until that logical change is complete and 
tested; with the working resource feature, all clients use a common set 
of shared version-controlled resources and every client sees the result 
of a MOVE as soon as it occurs.<a class="self" href="#rfc.section.9.p.1">¶</a></p></div><div id="rfc.section.9.p.2"><p>If
 a server supports the working-resource feature but not the 
checkout-in-place feature, a CHECKOUT request can only be used to create
 a working resource, and cannot be used to check out a 
version-controlled resource. If a server supports the checkout-in-place 
feature, but not the working-resource feature, a CHECKOUT can only be 
used to change the state of a version-controlled resource from 
checked-in to checked-out.<a class="self" href="#rfc.section.9.p.2">¶</a></p></div><section id="n-additional-version-properties_4"><h3 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#n-additional-version-properties_4">Additional Version Properties</a></h3><div id="rfc.section.9.1.p.1"><p>The working-resource feature introduces the following <em class="bcp14">REQUIRED</em> properties for a version.<a class="self" href="#rfc.section.9.1.p.1">¶</a></p></div><section id="n-dav-checkout-fork_2"><h4 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a href="#n-dav-checkout-fork_2">DAV:checkout-fork</a></h4><div id="rfc.section.9.1.1.p.1"><p>This property is defined in <a href="#PROPERTY_checkout-fork" title="DAV:checkout-fork">Section&nbsp;4.1.1</a>.<a class="self" href="#rfc.section.9.1.1.p.1">¶</a></p></div></section><section id="n-dav-checkin-fork_2"><h4 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a href="#n-dav-checkin-fork_2">DAV:checkin-fork</a></h4><div id="rfc.section.9.1.2.p.1"><p>This property is defined in <a href="#PROPERTY_checkin-fork" title="DAV:checkin-fork">Section&nbsp;4.1.2</a>.<a class="self" href="#rfc.section.9.1.2.p.1">¶</a></p></div></section></section><section id="n-working-resource-properties"><h3 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#n-working-resource-properties">Working Resource Properties</a></h3><div id="rfc.section.9.2.p.1"><p>The working-resource feature introduces the following <em class="bcp14">REQUIRED</em>
 properties for a working resource. Since a working resource is a 
checked-out resource, it also has any property defined in this document 
for a checked-out resource.<a class="self" href="#rfc.section.9.2.p.1">¶</a></p></div><section id="PROPERTY_auto-update"><h4 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a href="#PROPERTY_auto-update">DAV:auto-update (protected)</a></h4><div id="rfc.section.9.2.1.p.1"><p>This property identifies the version-controlled resource that will be updated when the working resource is checked in. <a class="self" href="#rfc.section.9.2.1.p.1">¶</a></p><span id="rfc.figure.u.80"><pre class="inline">&lt;!ELEMENT auto-update (href)&gt;
</pre></span></div></section><section id="n-dav-checkout-fork_3"><h4 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a href="#n-dav-checkout-fork_3">DAV:checkout-fork</a></h4><div id="rfc.section.9.2.2.p.1"><p>This property is defined in <a href="#PROPERTY_checkout-fork" title="DAV:checkout-fork">Section&nbsp;4.1.1</a>.<a class="self" href="#rfc.section.9.2.2.p.1">¶</a></p></div></section><section id="n-dav-checkin-fork_3"><h4 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;<a href="#n-dav-checkin-fork_3">DAV:checkin-fork</a></h4><div id="rfc.section.9.2.3.p.1"><p>This property is defined in <a href="#PROPERTY_checkin-fork" title="DAV:checkin-fork">Section&nbsp;4.1.2</a>.<a class="self" href="#rfc.section.9.2.3.p.1">¶</a></p></div></section></section><section id="n-checkout-method--applied-to-a-version-"><h3 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#n-checkout-method--applied-to-a-version-">CHECKOUT Method (applied to a version)</a></h3><div id="rfc.section.9.3.p.1"><p>A
 CHECKOUT request can be applied to a version to create a new working 
resource. The content and dead properties of the working resource are a 
copy of the version that was checked out.<a class="self" href="#rfc.section.9.3.p.1">¶</a></p></div><div id="rfc.section.9.3.p.2"><p><span id="rfc.iref.c.100"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.9.3.p.2">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:checkout XML element. <span id="rfc.figure.u.81"><pre class="inline">&lt;!ELEMENT checkout ANY&gt;

ANY value: A sequence of elements with at most one DAV:apply-to-version
and at most one DAV:fork-ok element.
&lt;!ELEMENT apply-to-version EMPTY&gt;
&lt;!ELEMENT fork-ok EMPTY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:checkout-response XML element. <span id="rfc.figure.u.82"><pre class="inline">&lt;!ELEMENT checkout-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Location header.</li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.9.3.p.3"><p><span id="rfc.iref.c.101"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.9.3.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.90"></span> <span id="rfc.iref.c.102"></span> (DAV:checkout-of-version-with-descendant-is-forbidden): See <a href="#checkout.method.applied.to.a.version-controlled.resource" title="CHECKOUT Method (applied to a version-controlled resource)">Section&nbsp;4.3</a>.</li><li><span id="rfc.iref.d.91"></span> <span id="rfc.iref.c.103"></span> (DAV:checkout-of-version-with-descendant-is-discouraged): See <a href="#checkout.method.applied.to.a.version-controlled.resource" title="CHECKOUT Method (applied to a version-controlled resource)">Section&nbsp;4.3</a>.</li><li><span id="rfc.iref.d.92"></span> <span id="rfc.iref.c.104"></span> (DAV:checkout-of-checked-out-version-is-forbidden): See <a href="#checkout.method.applied.to.a.version-controlled.resource" title="CHECKOUT Method (applied to a version-controlled resource)">Section&nbsp;4.3</a>.</li><li><span id="rfc.iref.d.93"></span> <span id="rfc.iref.c.105"></span> (DAV:checkout-of-checked-out-version-is-discouraged): See <a href="#checkout.method.applied.to.a.version-controlled.resource" title="CHECKOUT Method (applied to a version-controlled resource)">Section&nbsp;4.3</a>.</li></ul></div><div id="rfc.section.9.3.p.4"><p><span id="rfc.iref.c.106"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.9.3.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.94"></span> <span id="rfc.iref.c.107"></span> (DAV:create-working-resource): If the request-URL identified a version, the Location response header <em class="bcp14">MUST</em> contain the URL of a new working resource. The DAV:checked-out property of the new working resource <em class="bcp14">MUST</em> identify the version that was checked out. The content and dead properties of the working resource <em class="bcp14">MUST</em>
 be copies of the content and dead properties of the DAV:checked-out 
version. The DAV:predecessor-set property of the working resource <em class="bcp14">MUST</em> be initialized to be the version identified by the request-URL. The DAV:auto-update property of the working resource <em class="bcp14">MUST NOT</em> exist.</li><li><span id="rfc.iref.d.95"></span> <span id="rfc.iref.c.108"></span>
 (DAV:create-working-resource-from-checked-in-version): If the 
request-URL identified a version-controlled resource, and 
DAV:apply-to-version is specified in the request body, the CHECKOUT is 
applied to the DAV:checked-in version of the version-controlled 
resource, and not the version-controlled resource itself. A new working 
resource is created and the version-controlled resource remains 
checked-in. The DAV:auto-update property of the working resource <em class="bcp14">MUST</em> identify the version-controlled resource.</li></ul></div><section id="n-example---checkout-of-a-version"><h4 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a href="#n-example---checkout-of-a-version">Example - CHECKOUT of a version</a></h4><div id="rfc.figure.u.83"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKOUT /his/12/ver/V3 HTTP/1.1
Host: repo.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.84"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Location: http://repo.webdav.org/wr/157
Cache-Control: no-cache
</pre></div><div id="rfc.section.9.3.1.p.1"><p>In this example, the 
version identified by http://repo.webdav.org/his/12/ver/V3 is checked 
out, and the new working resource is located at 
http://repo.webdav.org/wr/157.<a class="self" href="#rfc.section.9.3.1.p.1">¶</a></p></div></section></section><section id="n-checkin-method--applied-to-a-working-resource-"><h3 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#n-checkin-method--applied-to-a-working-resource-">CHECKIN Method (applied to a working resource)</a></h3><div id="rfc.section.9.4.p.1"><p>A
 CHECKIN request can be applied to a working resource to produce a new 
version whose content and dead properties are a copy of those of the 
working resource. If the DAV:auto-update property of the working 
resource was set because the working resource was created by applying a 
CHECKOUT with the DAV:apply-to-version flag to a version-controlled 
resource, the CHECKIN request will also update the content and dead 
properties of that version-controlled resource to be those of the new 
version.<a class="self" href="#rfc.section.9.4.p.1">¶</a></p></div><div id="rfc.section.9.4.p.2"><p><span id="rfc.iref.c.109"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.9.4.p.2">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:checkin XML element. <span id="rfc.figure.u.85"><pre class="inline">&lt;!ELEMENT checkin ANY&gt;
ANY value: A sequence of elements with at most one DAV:fork-ok
element.

&lt;!ELEMENT fork-ok EMPTY&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:checkin-response XML element. <span id="rfc.figure.u.86"><pre class="inline">&lt;!ELEMENT checkin-response ANY&gt;
</pre></span> The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.9.4.p.3"><p><span id="rfc.iref.c.110"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.9.4.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.96"></span> <span id="rfc.iref.c.111"></span> (DAV:must-be-checked-out): See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.97"></span> <span id="rfc.iref.c.112"></span> (DAV:version-history-is-tree) See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.98"></span> <span id="rfc.iref.c.113"></span> (DAV:checkin-fork-forbidden): See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.99"></span> <span id="rfc.iref.c.114"></span> (DAV:checkin-fork-discouraged): See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.100"></span> <span id="rfc.iref.c.115"></span>
 (DAV:no-overwrite-by-auto-update): If the DAV:auto-update property for 
the checked-out resource identifies a version-controlled resource, at 
least one of the versions identified by the DAV:predecessor-set property
 of the checked-out resource <em class="bcp14">MUST</em> identify a 
version that is either the same as or a descendant of the version 
identified by the DAV:checked-in property of that version-controlled 
resource.</li></ul></div><div id="rfc.section.9.4.p.4"><p><span id="rfc.iref.c.116"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.9.4.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.101"></span> <span id="rfc.iref.c.117"></span> (DAV:create-version): See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.102"></span> <span id="rfc.iref.c.118"></span> (DAV:initialize-version-content-and-properties): See <a href="#checkin.method.applied.to.a.version-controlled.resource" title="CHECKIN Method (applied to a version-controlled resource)">Section&nbsp;4.4</a>.</li><li><span id="rfc.iref.d.103"></span> <span id="rfc.iref.c.119"></span>
 (DAV:auto-update): If the DAV:auto-update property of the checked-out 
resource identified a version-controlled resource, an UPDATE request 
with the new version <em class="bcp14">MUST</em> have been applied to that version-controlled resource.</li><li><span id="rfc.iref.d.104"></span> <span id="rfc.iref.c.120"></span>
 (DAV:delete-working-resource): If the request-URL identifies a working 
resource and if DAV:keep-checked-out is not specified in the request 
body, the working resource is deleted.</li></ul></div><section id="n-example---checkin-of-a-working-resource"><h4 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;<a href="#n-example---checkin-of-a-working-resource">Example - CHECKIN of a working resource</a></h4><div id="rfc.figure.u.87"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKIN /wr/157 HTTP/1.1
Host: repo.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.88"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Location: http://repo.webdav.org/his/23/ver/15
Cache-Control: no-cache
</pre></div><div id="rfc.section.9.4.1.p.1"><p>In this example, the working resource /wr/157 checked in, and a new version is created at http://repo.webdav.org/his/23/ver/15.<a class="self" href="#rfc.section.9.4.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_6"><h3 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#n-additional-options-semantics_6">Additional OPTIONS Semantics</a></h3><div id="rfc.section.9.5.p.1"><p>If the server supports the working-resource feature, it <em class="bcp14">MUST</em>
 include "working-resource" as a field in the DAV response header from 
an OPTIONS request on any resource that supports any versioning 
properties, reports, or methods.<a class="self" href="#rfc.section.9.5.p.1">¶</a></p></div></section><section id="n-additional-copy-semantics_4"><h3 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#n-additional-copy-semantics_4">Additional COPY Semantics</a></h3><div id="rfc.section.9.6.p.1"><p><span id="rfc.iref.c.121"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.9.6.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.105"></span> <span id="rfc.iref.c.122"></span>
 (DAV:copy-creates-new-resource): The result of copying a working 
resource is a new non-version-controlled resource at the destination of 
the COPY. The new resource <em class="bcp14">MAY</em> automatically be put under version control, but the resulting version-controlled resource <em class="bcp14">MUST</em> be associated with a new version history created for that new version-controlled resource.</li></ul></div></section><section id="n-additional-move-semantics_4"><h3 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#n-additional-move-semantics_4">Additional MOVE Semantics</a></h3><div id="rfc.section.9.7.p.1"><p><span id="rfc.iref.m.9"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.9.7.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.106"></span> <span id="rfc.iref.c.123"></span> (DAV:cannot-rename-working-resource): If the request-URL identifies a working resource, the request <em class="bcp14">MUST</em> fail.</li></ul></div><div id="rfc.section.9.7.p.2"><p><span id="rfc.iref.m.10"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.9.7.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.107"></span> <span id="rfc.iref.c.124"></span>
 (DAV:update-auto-update): If the request-URL identified a 
version-controlled resource, any DAV:auto-update properties that 
identified that version-controlled resource <em class="bcp14">MUST</em> have been updated to contain the new location of that version-controlled resource.</li></ul></div></section></section><hr class="noprint"><section id="advanced.versioning.features"><h2 id="rfc.section.10" class="np"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#advanced.versioning.features">Advanced Versioning Features</a></h2><div id="rfc.section.10.p.1"><p>Advanced
 versioning addresses the problems of parallel development and 
configuration management of multiple sets of interrelated resources. 
Traditionally, artifacts of software development, including 
requirements, design documents, code, and test cases, have been a focus 
of configuration management. Web sites, comprising multiple inter-linked
 resources (HTML, graphics, sound, CGI, and others), are another class 
of complex information artifacts that benefit from the application of 
configuration management. The advanced versioning capabilities for 
coordinating concurrent change provide the infrastructure for efficient 
and controlled management of large evolving web sites.<a class="self" href="#rfc.section.10.p.1">¶</a></p></div><section id="n-advanced-versioning-packages"><h3 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a href="#n-advanced-versioning-packages">Advanced Versioning Packages</a></h3><div id="rfc.section.10.1.p.1" class="avoidbreakafter"><p>Although a server <em class="bcp14">MAY</em>
 support any combination of advanced versioning features, in order to 
minimize the complexity of a WebDAV advanced versioning client, a WebDAV
 advanced versioning server <em class="bcp14">SHOULD</em> support one of the following packages:<a class="self" href="#rfc.section.10.1.p.1">¶</a></p></div><div id="rfc.section.10.1.p.2"><p>Advanced-Server-Workspace Package: basic-server-workspace package plus all advanced features<a class="self" href="#rfc.section.10.1.p.2">¶</a></p></div><div id="rfc.section.10.1.p.3"><p>Advanced-Client-Workspace Package: basic-client-workspace package plus all advanced features<a class="self" href="#rfc.section.10.1.p.3">¶</a></p></div><div id="rfc.section.10.1.p.4"><p>The
 advanced-server-workspace package supports advanced versioning 
capabilities for a client with no persistent state. The 
advanced-client-workspace package supports advanced versioning 
capabilities for a client that maintains configuration state on the 
client. A server that supports both advanced workspace packages will 
interoperate with all versioning clients.<a class="self" href="#rfc.section.10.1.p.4">¶</a></p></div></section><section id="n-advanced-versioning-terms"><h3 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a href="#n-advanced-versioning-terms">Advanced Versioning Terms</a></h3><div id="rfc.section.10.2.p.1"><p>The following additional terms are used by the advanced versioning features.<a class="self" href="#rfc.section.10.2.p.1">¶</a></p></div><div id="rfc.section.10.2.p.2"><p><dfn>Collection</dfn><span id="rfc.iref.c.125"></span> <a class="self" href="#rfc.section.10.2.p.2">¶</a></p><ul class="empty"><li>A
 "collection" is a resource whose state consists of not only content and
 properties, but also a set of named "bindings", where a binding 
identifies what RFC 2518 calls an "internal member" of the collection. 
Note that a binding is not a resource, but rather is a part of the state
 of a collection that defines a mapping from a binding name (a URL 
segment) to a resource (an internal member of the collection).</li></ul></div><div id="rfc.section.10.2.p.3"><p><dfn>Collection Version Resource</dfn><span id="rfc.iref.c.126"></span> <a class="self" href="#rfc.section.10.2.p.3">¶</a></p><ul class="empty"><li>A
 "collection version resource", or simply "collection version", captures
 the dead properties of a version-controlled collection, as well as the 
names of its version-controlled bindings (see <a href="#version-controlled-collection.feature" title="Version-Controlled-Collection Feature">Section&nbsp;14</a>).
 A version-controlled binding is a binding to a version-controlled 
resource. If the checkout-in-place feature is supported, a collection 
version can be created by checking out and then checking in a 
version-controlled collection. If the working-resource feature is 
supported, a collection version can be created by checking out a 
collection version (to create a "working collection") and then checking 
in the working collection.</li></ul></div><div id="rfc.section.10.2.p.4"><p><dfn>Configuration</dfn><span id="rfc.iref.c.127"></span> <a class="self" href="#rfc.section.10.2.p.4">¶</a></p><ul class="empty"><li>A
 "configuration" is a set of resources that consists of a root 
collection and all members (not just internal members) of that root 
collection that are not members of another configuration. The root 
collection is called the "configuration root", and the members of this 
set are called the "members of the configuration". Note that a 
collection (which is a single resource) is very different from a 
configuration (which is a set of resources).</li></ul></div><div id="rfc.section.10.2.p.5"><p><dfn>Baseline Resource</dfn><span id="rfc.iref.b.1"></span> <a class="self" href="#rfc.section.10.2.p.5">¶</a></p><ul class="empty"><li>A
 "baseline resource", or simply "baseline", of a collection is a version
 of the configuration that is rooted at that collection (see <a href="#baseline.feature" title="Baseline Feature">Section&nbsp;12</a>).
 In particular, a baseline captures the DAV:checked-in version of every 
version-controlled member of that configuration. Note that a collection 
version (which captures the state of a single resource) is very 
different from a collection baseline (which captures the state of a set 
of resources).</li></ul></div><div id="rfc.section.10.2.p.6"><p><dfn>Baseline-Controlled Collection</dfn><span id="rfc.iref.b.2"></span> <a class="self" href="#rfc.section.10.2.p.6">¶</a></p><ul class="empty"><li>A "baseline-controlled collection" is a collection from which baselines can be created (see <a href="#baseline.feature" title="Baseline Feature">Section&nbsp;12</a>).</li></ul></div><div id="rfc.section.10.2.p.7"><p><dfn>Version-Controlled Configuration Resource</dfn><span id="rfc.iref.v.13"></span> <a class="self" href="#rfc.section.10.2.p.7">¶</a></p><ul class="empty"><li>A
 "version-controlled configuration resource", or simply 
"version-controlled configuration", is a special kind of 
version-controlled resource that is associated with a 
baseline-controlled collection, and is used to create and access 
baselines of that collection (see <a href="#baseline.feature" title="Baseline Feature">Section&nbsp;12</a>).
 When a collection is both version-controlled and baseline-controlled, a
 client can create a new version of the collection by checking out and 
checking in that collection, and it can create a new baseline of that 
collection by checking out and checking in the version-controlled 
configuration of that collection.</li></ul></div><div id="rfc.section.10.2.p.8"><p><dfn>Activity Resource</dfn><span id="rfc.iref.a.2"></span> <a class="self" href="#rfc.section.10.2.p.8">¶</a></p><ul class="empty"><li>An
 "activity resource", or simply "activity", is a resource that selects a
 set of versions that correspond to a single logical change, where the 
versions selected from a given version history form a single line of 
descent through that version history (see <a href="#activity.feature" title="Activity Feature">Section&nbsp;13</a>).</li></ul></div></section></section><hr class="noprint"><section id="merge.feature"><h2 id="rfc.section.11" class="np"><a href="#rfc.section.11">11.</a>&nbsp;<a href="#merge.feature">Merge Feature</a></h2><div id="rfc.section.11.p.1"><p>When
 a user wants to accept the changes (new versions) created by someone 
else, it is important not just to update the version-controlled 
resources in the user's workspace with those new versions, since this 
could result in "backing out" changes the user has made to those 
version-controlled resources. Instead, the versions created in another 
workspace should be "merged" into the user's version-controlled 
resources.<a class="self" href="#rfc.section.11.p.1">¶</a></p></div><div id="rfc.section.11.p.2"><p>The
 version history of a version-controlled resource provides the 
information needed to determine the result of the merge. In particular, 
the merge should select whichever version is later in the line of 
descent from the root version. In case the versions to be merged are on 
different lines of descent (neither version is a descendant of the 
other), neither version should be selected, but instead, a new version 
should be created that contains the logical merge of the content and 
dead properties of those versions. The MERGE request can be used to 
check out each version-controlled resource that requires such a merge, 
and set the DAV:merge-set property of each checked-out resource to 
identify the version to be merged. The user is responsible for modifying
 the content and dead properties of the checked-out resource so that it 
represents the logical merge of that version, and then adding that 
version to the DAV:predecessor-set of the checked-out resource.<a class="self" href="#rfc.section.11.p.2">¶</a></p></div><div id="rfc.section.11.p.3"><p>If the server is capable of automatically performing the merge, it <em class="bcp14">MAY</em>
 update the content, dead properties, and DAV:predecessor-set of the 
checked-out resource itself. Before checking in the automatically merged
 resource, the user is responsible for verifying that the automatic 
merge is correct.<a class="self" href="#rfc.section.11.p.3">¶</a></p></div><section id="n-additional-checked-out-resource-properties_1"><h3 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a href="#n-additional-checked-out-resource-properties_1">Additional Checked-Out Resource Properties</a></h3><div id="rfc.section.11.1.p.1"><p>The merge feature introduces the following <em class="bcp14">REQUIRED</em> properties for a checked-out resource.<a class="self" href="#rfc.section.11.1.p.1">¶</a></p></div><section id="PROPERTY_merge-set"><h4 id="rfc.section.11.1.1"><a href="#rfc.section.11.1.1">11.1.1</a>&nbsp;<a href="#PROPERTY_merge-set">DAV:merge-set</a></h4><div id="rfc.section.11.1.1.p.1"><p>This property identifies each version that is to be merged into this checked-out resource. <a class="self" href="#rfc.section.11.1.1.p.1">¶</a></p><span id="rfc.figure.u.89"><pre class="inline">&lt;!ELEMENT merge-set (href*)&gt;
</pre></span></div></section><section id="PROPERTY_auto-merge-set"><h4 id="rfc.section.11.1.2"><a href="#rfc.section.11.1.2">11.1.2</a>&nbsp;<a href="#PROPERTY_auto-merge-set">DAV:auto-merge-set</a></h4><div id="rfc.section.11.1.2.p.1"><p>This
 property identifies each version that the server has merged into this 
checked-out resource. The client should confirm that the merge has been 
performed correctly before moving a URL from the DAV:auto-merge-set to 
the DAV:predecessor-set of a checked-out resource. <a class="self" href="#rfc.section.11.1.2.p.1">¶</a></p><span id="rfc.figure.u.90"><pre class="inline">&lt;!ELEMENT auto-merge-set (href*)&gt;
</pre></span></div></section></section><section id="METHOD_MERGE"><h3 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a href="#METHOD_MERGE">MERGE Method</a></h3><div id="rfc.section.11.2.p.1"><p>The
 MERGE method performs the logical merge of a specified version (the 
"merge source") into a specified version-controlled resource (the "merge
 target"). If the merge source is neither an ancestor nor a descendant 
of the DAV:checked-in or DAV:checked-out version of the merge target, 
the MERGE checks out the merge target (if it is not already checked out)
 and adds the URL of the merge source to the DAV:merge-set of the merge 
target. It is then the client's responsibility to update the content and
 dead properties of the checked-out merge target so that it reflects the
 logical merge of the merge source into the current state of the merge 
target. The client indicates that it has completed the update of the 
merge target, by deleting the merge source URL from the DAV:merge-set of
 the checked-out merge target, and adding it to the DAV:predecessor-set.
 As an error check for a client forgetting to complete a merge, the 
server <em class="bcp14">MUST</em> fail an attempt to CHECKIN a version-controlled resource with a non-empty DAV:merge-set.<a class="self" href="#rfc.section.11.2.p.1">¶</a></p></div><div id="rfc.section.11.2.p.2"><p>When
 a server has the ability to automatically update the content and dead 
properties of the merge target to reflect the logical merge of the merge
 source, it may do so unless DAV:no-auto-merge is specified in the MERGE
 request body. In order to notify the client that a merge source has 
been automatically merged, the MERGE request <em class="bcp14">MUST</em>
 add the URL of the auto-merged source to the DAV:auto-merge-set 
property of the merge target, and not to the DAV:merge-set property. The
 client indicates that it has verified that the auto-merge is valid, by 
deleting the merge source URL from the DAV:auto-merge-set, and adding it
 to the DAV:predecessor-set.<a class="self" href="#rfc.section.11.2.p.2">¶</a></p></div><div id="rfc.section.11.2.p.3" class="avoidbreakafter"><p>Multiple
 merge sources can be specified in a single MERGE request. The set of 
merge sources for a MERGE request is determined from the DAV:source 
element of the MERGE request body as follows:<a class="self" href="#rfc.section.11.2.p.3">¶</a></p></div><div id="rfc.section.11.2.p.4"><ul><li>If DAV:source identifies a version, that version is a merge source.</li><li>If
 DAV:source identifies a version-controlled resource, the DAV:checked-in
 version of that version-controlled resource is a merge source.</li><li>If
 DAV:source identifies a collection, the DAV:checked-in version of each 
version-controlled resource that is a member of that collection is a 
merge source.</li></ul></div><div id="rfc.section.11.2.p.5"><p>The 
request-URL identifies the set of possible merge targets. If the 
request-URL identifies a collection, any member of the configuration 
rooted at the request-URL is a possible merge target. The merge target 
of a particular merge source is the version-controlled or checked-out 
resource whose DAV:checked-in or DAV:checked-out version is from the 
same version history as the merge source. If a merge source has no merge
 target, that merge source is ignored.<a class="self" href="#rfc.section.11.2.p.5">¶</a></p></div><div id="rfc.section.11.2.p.6"><p>The
 MERGE response identifies the resources that a client must modify to 
complete the merge. It also identifies the resources modified by the 
request, so that a client can efficiently update any cached state it is 
maintaining.<a class="self" href="#rfc.section.11.2.p.6">¶</a></p></div><div id="rfc.section.11.2.p.7"><p><span id="rfc.iref.m.11"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.11.2.p.7">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:merge element.</li><li>The set of merge sources is determined by the DAV:source element in the request body. <span id="rfc.figure.u.91"><pre class="inline">&lt;!ELEMENT merge ANY&gt;
ANY value: A sequence of elements with one DAV:source element, at
most one DAV:no-auto-merge element, at most one DAV:no-checkout
element, at most one DAV:prop element, and any legal set of
elements that can occur in a DAV:checkout element.
&lt;!ELEMENT source (href+)&gt;
&lt;!ELEMENT no-auto-merge EMPTY&gt;
&lt;!ELEMENT no-checkout EMPTY&gt;
prop: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.11" id="rfc.xref.RFC2518.10">Section 12.11</a>
</pre></span> </li><li>The response for a successful request <em class="bcp14">MUST</em>
 be a 207 Multi-Status, where the DAV:multistatus XML element in the 
response body identifies all resources that have been modified by the 
request. <span id="rfc.figure.u.92"><pre class="inline">multistatus: see RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-12.9" id="rfc.xref.RFC2518.11">Section 12.9</a>
</pre></span> </li><li>The response to a successful request <em class="bcp14">MUST</em> include a Location header containing the URL for the new version created by the checkin.</li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.11.2.p.8"><p><span id="rfc.iref.m.12"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.11.2.p.8">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.108"></span> <span id="rfc.iref.c.128"></span> (DAV:cannot-merge-checked-out-resource): The DAV:source element <em class="bcp14">MUST NOT</em> identify a checked-out resource. If the DAV:source element identifies a collection, the collection <em class="bcp14">MUST NOT</em> have a member that is a checked-out resource.</li><li><span id="rfc.iref.d.109"></span> <span id="rfc.iref.c.129"></span> (DAV:checkout-not-allowed): If DAV:no-checkout is specified in the request body, it <em class="bcp14">MUST</em> be possible to perform the merge without checking out any of the merge targets.</li><li>All preconditions of the CHECKOUT operation apply to the checkouts performed by the request.</li></ul></div><div id="rfc.section.11.2.p.9"><p><span id="rfc.iref.m.13"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.11.2.p.9">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.110"></span> <span id="rfc.iref.c.130"></span>
 (DAV:ancestor-version): If a merge target is a version-controlled or 
checked-out resource whose DAV:checked-in version or DAV:checked-out 
version is the merge source or is a descendant of the merge source, the 
merge target <em class="bcp14">MUST NOT</em> have been modified by the MERGE.</li><li><span id="rfc.iref.d.111"></span> <span id="rfc.iref.c.131"></span>
 (DAV:descendant-version): If the merge target was a checked-in 
version-controlled resource whose DAV:checked-in version was an ancestor
 of the merge source, an UPDATE operation <em class="bcp14">MUST</em> 
have been applied to the merge target to set its content and dead 
properties to be those of the merge source. If the UPDATE method is not 
supported, the merge target <em class="bcp14">MUST</em> have been checked out, the content and dead properties of the merge target <em class="bcp14">MUST</em> have been set to those of the merge source, and the merge source <em class="bcp14">MUST</em> have been added to the DAV:auto-merge-set of the merge target. The merge target <em class="bcp14">MUST</em> appear in a DAV:response XML element in the response body.</li><li><span id="rfc.iref.d.112"></span> <span id="rfc.iref.c.132"></span>
 (DAV:checked-out-for-merge): If the merge target was a checked-in 
version-controlled resource whose DAV:checked-in version was neither a 
descendant nor an ancestor of the merge source, a CHECKOUT <em class="bcp14">MUST</em>
 have been applied to the merge target. All XML elements in the 
DAV:merge XML element that could appear in a DAV:checkout XML element <em class="bcp14">MUST</em> have been used as arguments to the CHECKOUT request. The merge target <em class="bcp14">MUST</em> appear in a DAV:response XML element in the response body.</li><li><span id="rfc.iref.d.113"></span> <span id="rfc.iref.c.133"></span>
 (DAV:update-merge-set): If the DAV:checked-out version of the merge 
target is neither equal to nor a descendant of the merge source, the 
merge source <em class="bcp14">MUST</em> be added to either the DAV:merge-set or the DAV:auto-merge-set of the merge target. The merge target <em class="bcp14">MUST</em> appear in a DAV:response XML element in the response body.</li><li>If a merge source has been added to the DAV:auto-merge-set, the content and dead properties of the merge target <em class="bcp14">MUST</em>
 have been modified by the server to reflect the result of a logical 
merge of the merge source and the merge target. If a merge source has 
been added to the DAV:merge-set, the content and dead properties of the 
merge target <em class="bcp14">MUST NOT</em> have been modified by the server. If DAV:no-auto-merge is specified in the request body, the merge source <em class="bcp14">MUST NOT</em> have been added to the DAV:auto-merge-set.</li><li><span id="rfc.iref.d.114"></span> <span id="rfc.iref.c.134"></span> (DAV:report-properties): If DAV:prop is specified in the request body, the properties specified in the DAV:prop element <em class="bcp14">MUST</em> be reported in the DAV:response elements in the response body.</li></ul></div><section id="n-example---merge"><h4 id="rfc.section.11.2.1"><a href="#rfc.section.11.2.1">11.2.1</a>&nbsp;<a href="#n-example---merge">Example - MERGE</a></h4><div id="rfc.figure.u.93"><p>&gt;&gt;REQUEST</p><pre class="text2">MERGE /ws/public HTTP/1.1
Host: www.webdav.org
Content-type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:merge xmlns:D="DAV:"&gt;
  &lt;D:source&gt;
    &lt;D:href&gt;http://www.webdav.org/ws/dev/sally&lt;/D:href&gt;
  &lt;/D:source&gt;
&lt;/D:merge&gt;
</pre></div><div id="rfc.figure.u.94"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx
Cache-Control: no-cache

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:multistatus xmlns:D="DAV:"&gt;
  &lt;D:response&gt;
    &lt;D:href&gt;http://www.webdav.org/ws/public/src/parse.c&lt;/D:href&gt;
    &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
  &lt;/D:response&gt;
  &lt;D:response&gt;
    &lt;D:href&gt;http://www.webdav.org/ws/public/doc/parse.html&lt;/D:href&gt;
    &lt;D:status&gt;HTTP/1.1 200 OK&lt;/D:status&gt;
  &lt;/D:response&gt;
&lt;/D:multistatus&gt;
</pre></div><div id="rfc.section.11.2.1.p.1"><p>In this example, the 
DAV:checked-in versions from the workspace 
http://www.webdav.org/ws/dev/sally are merged into the 
version-controlled resources in the workspace 
http://www.webdav.org/ws/public. The resources /ws/public/src/parse.c 
and /ws/public/doc/parse.html were modified by the request.<a class="self" href="#rfc.section.11.2.1.p.1">¶</a></p></div></section></section><section id="n-dav-merge-preview-report"><h3 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a href="#n-dav-merge-preview-report">DAV:merge-preview Report</a></h3><div id="rfc.section.11.3.p.1"><p>A
 merge preview describes the changes that would result if the versions 
specified by the DAV:source element in the request body were to be 
merged into the resource identified by the request-URL (commonly, a 
collection).<a class="self" href="#rfc.section.11.3.p.1">¶</a></p></div><div id="rfc.section.11.3.p.2"><p><span id="rfc.iref.d.115"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.11.3.p.2">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:merge-preview XML element. <span id="rfc.figure.u.95"><pre class="inline">&lt;!ELEMENT merge-preview (source)&gt;
&lt;!ELEMENT source (href)&gt;
</pre></span> </li><li>The response body for a successful request <em class="bcp14">MUST</em> be a DAV:merge-preview-report XML element. <span id="rfc.figure.u.96"><pre class="inline">&lt;!ELEMENT merge-preview-report
(update-preview | conflict-preview | ignore-preview)*&gt;
</pre></span> </li><li>A DAV:update-preview element identifies a merge 
target whose DAV:checked-in property would change as a result of the 
MERGE, and identifies the merge source for that merge target. <span id="rfc.figure.u.97"><pre class="inline">&lt;!ELEMENT update-preview (target, version)&gt;
&lt;!ELEMENT target (href)&gt;
&lt;!ELEMENT version (href)&gt;
</pre></span> </li><li>A DAV:conflict-preview element identifies a merge target that requires a merge. <span id="rfc.figure.u.98"><pre class="inline">&lt;!ELEMENT conflict-preview (target, common-ancestor, version)&gt;
</pre></span> </li><li>A DAV:common-ancestor element identifies the 
version that is a common ancestor of both the merge source and the 
DAV:checked-in or DAV:checked-out version of the merge target. <span id="rfc.figure.u.99"><pre class="inline">&lt;!ELEMENT common-ancestor (href)&gt;
</pre></span> </li><li>A DAV:ignore-preview element identifies a version that has no merge target and therefore would be ignored by the merge. <span id="rfc.figure.u.100"><pre class="inline">&lt;!ELEMENT ignore-preview (version)&gt;
</pre></span></li></ul></div><section id="n-example---dav-merge-preview-report"><h4 id="rfc.section.11.3.1"><a href="#rfc.section.11.3.1">11.3.1</a>&nbsp;<a href="#n-example---dav-merge-preview-report">Example - DAV:merge-preview Report</a></h4><div id="rfc.figure.u.101"><p>&gt;&gt;REQUEST</p><pre class="text2">REPORT /ws/public HTTP/1.1
Host: www.webdav.org
Content-type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:merge-preview xmlns:D="DAV:"&gt;
  &lt;D:source&gt;
    &lt;D:href&gt;http://www.webdav.org/ws/dev/fred&lt;/D:href&gt;
  &lt;/D:source&gt;
&lt;/D:merge-preview&gt;
</pre></div><div id="rfc.figure.u.102"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:merge-preview-report xmlns:D="DAV:"&gt;
  &lt;D:conflict-preview&gt;
    &lt;D:target&gt;
      &lt;D:href&gt;http://www.webdav.org/ws/public/foo.html&lt;/D:href&gt;
    &lt;/D:target&gt;
    &lt;D:common-ancestor&gt;
      &lt;D:href&gt;http://repo.webdav.org/his/23/ver/18&lt;/D:href&gt;
    &lt;/D:common-ancestor&gt;
    &lt;D:version&gt;
      &lt;D:href&gt;http://repo.webdav.org/his/23/ver/42&lt;/D:href&gt;
    &lt;/D:version&gt;
  &lt;/D:conflict-preview&gt;
  &lt;D:update-preview&gt;
    &lt;D:target&gt;
      &lt;D:href&gt;http://www.webdav.org/ws/public/bar.html&lt;/D:href&gt;
    &lt;/D:target&gt;
    &lt;D:version&gt;
      &lt;D:href&gt;http://www.repo/his/42/ver/3&lt;/D:href&gt;
    &lt;/D:version&gt;
  &lt;/D:update-preview&gt;
&lt;/D:merge-preview-report&gt;
</pre></div><div id="rfc.section.11.3.1.p.1"><p>In this example, the 
merge preview report indicates that version /his/23/ver/42 would be 
merged in /ws/public/foo.html, and version /his/42/ver/3 would update 
/ws/public/bar.html if the workspace http://www.webdav.org/ws/dev/fred 
was merged into the workspace http://www.webdav.org/ws/public.<a class="self" href="#rfc.section.11.3.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_7"><h3 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a href="#n-additional-options-semantics_7">Additional OPTIONS Semantics</a></h3><div id="rfc.section.11.4.p.1"><p>If the server supports the merge feature, it <em class="bcp14">MUST</em>
 include "merge" as a field in the DAV response header from an OPTIONS 
request on any resource that supports any versioning properties, 
reports, or methods.<a class="self" href="#rfc.section.11.4.p.1">¶</a></p></div></section><section id="n-additional-delete-semantics_3"><h3 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a>&nbsp;<a href="#n-additional-delete-semantics_3">Additional DELETE Semantics</a></h3><div id="rfc.section.11.5.p.1"><p><span id="rfc.iref.d.116"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.11.5.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.117"></span> <span id="rfc.iref.c.135"></span>
 (DAV:delete-version-reference): If a version is deleted, any reference 
to that version in a DAV:merge-set or DAV:auto-merge-set property <em class="bcp14">MUST</em> be removed.</li></ul></div></section><section id="n-additional-checkin-semantics_2"><h3 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a>&nbsp;<a href="#n-additional-checkin-semantics_2">Additional CHECKIN Semantics</a></h3><div id="rfc.section.11.6.p.1"><p><span id="rfc.iref.c.136"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.11.6.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.118"></span> <span id="rfc.iref.c.137"></span> (DAV:merge-must-be-complete): The DAV:merge-set and DAV:auto-merge-set of the checked-out resource <em class="bcp14">MUST</em> be empty or not exist.</li></ul></div></section></section><hr class="noprint"><section id="baseline.feature"><h2 id="rfc.section.12" class="np"><a href="#rfc.section.12">12.</a>&nbsp;<a href="#baseline.feature">Baseline Feature</a></h2><div id="rfc.section.12.p.1"><p>A
 configuration is a set of resources that consists of a root collection 
and all members of that root collection except those resources that are 
members of another configuration. A configuration that contains a large 
number of resources can consume a large amount of space on a server. 
This can make it prohibitively expensive to remember the state of an 
existing configuration by creating a Depth:infinity copy of its root 
collection.<a class="self" href="#rfc.section.12.p.1">¶</a></p></div><div id="rfc.section.12.p.2"><p>A
 baseline is a version resource that captures the state of each 
version-controlled member of a configuration. A baseline history is a 
version history whose versions are baselines. New baselines are created 
by checking out and then checking in a special kind of 
version-controlled resource called a version-controlled configuration.<a class="self" href="#rfc.section.12.p.2">¶</a></p></div><div id="rfc.section.12.p.3"><p>A
 collection that is under baseline control is called a 
baseline-controlled collection. In order to allow efficient baseline 
implementation, the state of a baseline of a collection is limited to be
 a set of versions and their names relative to the collection, and the 
operations on a baseline are limited to the creation of a baseline from a
 collection, and restoring or merging the baseline back into a 
collection. A server <em class="bcp14">MAY</em> automatically put a 
collection under baseline control when it is created, or a client can 
use the BASELINE-CONTROL method to put a specified collection under 
baseline control.<a class="self" href="#rfc.section.12.p.3">¶</a></p></div><div id="rfc.section.12.p.4"><p>As
 a configuration gets large, it is often useful to break it up into a 
set of smaller configurations that form the logical "components" of that
 configuration. In order to capture the fact that a baseline of a 
configuration is logically extended by a component configuration 
baseline, the component configuration baseline is captured as a 
"subbaseline" of the baseline.<a class="self" href="#rfc.section.12.p.4">¶</a></p></div><div id="rfc.section.12.p.5"><p>The
 root collection of a configuration is unconstrained with respect to its
 relationship to the root collection of any of its components. In 
particular, the root collection of a configuration can have a member 
that is the root collection of one of its components (e.g., 
configuration /sys/x can have a component /sys/x/foo), can be a member 
of the root collection of one of its components (e.g., configuration 
/sys/y/z can have a component /sys/y), or neither (e.g., configuration 
/sys/x can have a component /comp/bar).<a class="self" href="#rfc.section.12.p.5">¶</a></p></div><section id="n-version-controlled-configuration-properties"><h3 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a href="#n-version-controlled-configuration-properties">Version-Controlled Configuration Properties</a></h3><div id="rfc.section.12.1.p.1"><p>Since
 a version-controlled configuration is a version-controlled resource, it
 has all the properties of a version-controlled resource. In addition, 
the baseline feature introduces the following <em class="bcp14">REQUIRED</em> property for a version-controlled configuration.<a class="self" href="#rfc.section.12.1.p.1">¶</a></p></div><section id="PROPERTY_baseline-controlled-collection"><h4 id="rfc.section.12.1.1"><a href="#rfc.section.12.1.1">12.1.1</a>&nbsp;<a href="#PROPERTY_baseline-controlled-collection">DAV:baseline-controlled-collection (protected)</a></h4><div id="rfc.section.12.1.1.p.1"><p>This
 property identifies the collection that contains the version-controlled
 resources whose DAV:checked-in versions are being tracked by this 
version-controlled configuration. The 
DAV:version-controlled-configuration of the 
DAV:baseline-controlled-collection of a version-controlled configuration
 <em class="bcp14">MUST</em> identify that version-controlled configuration. <a class="self" href="#rfc.section.12.1.1.p.1">¶</a></p><span id="rfc.figure.u.103"><pre class="inline">&lt;!ELEMENT baseline-controlled-collection (href)&gt;
</pre></span></div></section></section><section id="n-checked-out-configuration-properties"><h3 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a href="#n-checked-out-configuration-properties">Checked-Out Configuration Properties</a></h3><div id="rfc.section.12.2.p.1"><p>Since
 a checked-out configuration is a checked-out resource, it has all the 
properties of a checked-out resource. In addition, the baseline feature 
introduces the following <em class="bcp14">REQUIRED</em> property for a checked-out configuration.<a class="self" href="#rfc.section.12.2.p.1">¶</a></p></div><section id="PROPERTY_subbaseline-set"><h4 id="rfc.section.12.2.1"><a href="#rfc.section.12.2.1">12.2.1</a>&nbsp;<a href="#PROPERTY_subbaseline-set">DAV:subbaseline-set</a></h4><div id="rfc.section.12.2.1.p.1"><p>This property determines the DAV:subbaseline-set property of the baseline that results from checking in this resource.<a class="self" href="#rfc.section.12.2.1.p.1">¶</a></p></div><div id="rfc.section.12.2.1.p.2"><p>A server <em class="bcp14">MAY</em> reject attempts to modify the DAV:subbaseline-set of a checked-out configuration. <a class="self" href="#rfc.section.12.2.1.p.2">¶</a></p><span id="rfc.figure.u.104"><pre class="inline">&lt;!ELEMENT subbaseline-set (href*)&gt;
</pre></span></div></section></section><section id="n-baseline-properties"><h3 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a href="#n-baseline-properties">Baseline Properties</a></h3><div id="rfc.section.12.3.p.1"><p>The DAV:resourcetype of a baseline <em class="bcp14">MUST</em>
 be DAV:baseline. Since a baseline is a version resource, it has all the
 properties of a version resource. In addition, the baseline feature 
introduces the following <em class="bcp14">REQUIRED</em> properties for a baseline.<a class="self" href="#rfc.section.12.3.p.1">¶</a></p></div><section id="PROPERTY_baseline-collection"><h4 id="rfc.section.12.3.1"><a href="#rfc.section.12.3.1">12.3.1</a>&nbsp;<a href="#PROPERTY_baseline-collection">DAV:baseline-collection (protected)</a></h4><div id="rfc.section.12.3.1.p.1"><p>This property contains a server-defined URL for a collection, where each member of this collection <em class="bcp14">MUST</em>
 either be a version-controlled resource with the same DAV:checked-in 
version and relative name as a version-controlled member of the 
baseline-controlled collection at the time the baseline was created, or 
be a collection needed to provide the relative name for a 
version-controlled resource. <a class="self" href="#rfc.section.12.3.1.p.1">¶</a></p><span id="rfc.figure.u.105"><pre class="inline">&lt;!ELEMENT baseline-collection (href)&gt;
</pre></span></div></section><section id="n-dav-subbaseline-set--protected-"><h4 id="rfc.section.12.3.2"><a href="#rfc.section.12.3.2">12.3.2</a>&nbsp;<a href="#n-dav-subbaseline-set--protected-">DAV:subbaseline-set (protected)</a></h4><div id="rfc.section.12.3.2.p.1"><p>The URLs in the DAV:subbaseline-set property <em class="bcp14">MUST</em>
 identify a set of other baselines. The subbaselines of a baseline are 
the baselines identified by its DAV:subbaseline-set and all subbaselines
 of the baselines identified by its DAV:subbaseline-set. <a class="self" href="#rfc.section.12.3.2.p.1">¶</a></p><span id="rfc.figure.u.106"><pre class="inline">&lt;!ELEMENT subbaseline-set (href*)&gt;
</pre></span></div></section></section><section id="n-additional-resource-properties_3"><h3 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;<a href="#n-additional-resource-properties_3">Additional Resource Properties</a></h3><div id="rfc.section.12.4.p.1"><p>The baseline feature introduces the following <em class="bcp14">REQUIRED</em> property for a resource.<a class="self" href="#rfc.section.12.4.p.1">¶</a></p></div><section id="PROPERTY_version-controlled-configuration"><h4 id="rfc.section.12.4.1"><a href="#rfc.section.12.4.1">12.4.1</a>&nbsp;<a href="#PROPERTY_version-controlled-configuration">DAV:version-controlled-configuration (computed)</a></h4><div id="rfc.section.12.4.1.p.1"><p>If
 the resource is a member of a version-controlled configuration (i.e. 
the resource is a collection under baseline control or is a member of a 
collection under baseline control), this property identifies that 
version-controlled configuration. <a class="self" href="#rfc.section.12.4.1.p.1">¶</a></p><span id="rfc.figure.u.107"><pre class="inline">&lt;!ELEMENT version-controlled-configuration (href)&gt;
</pre></span></div></section></section><section id="n-additional-workspace-properties_1"><h3 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a>&nbsp;<a href="#n-additional-workspace-properties_1">Additional Workspace Properties</a></h3><div id="rfc.section.12.5.p.1"><p>The baseline feature introduces the following <em class="bcp14">REQUIRED</em> property for a workspace.<a class="self" href="#rfc.section.12.5.p.1">¶</a></p></div><section id="PROPERTY_baseline-controlled-collection-set"><h4 id="rfc.section.12.5.1"><a href="#rfc.section.12.5.1">12.5.1</a>&nbsp;<a href="#PROPERTY_baseline-controlled-collection-set">DAV:baseline-controlled-collection-set (computed)</a></h4><div id="rfc.section.12.5.1.p.1"><p>This
 property identifies each member of the workspace that is a collection 
under baseline control (as well as the workspace itself, if it is under 
baseline control). <a class="self" href="#rfc.section.12.5.1.p.1">¶</a></p><span id="rfc.figure.u.108"><pre class="inline">&lt;!ELEMENT baseline-controlled-collection-set (href*)&gt;
</pre></span></div></section></section><section id="METHOD_BASELINE-CONTROL"><h3 id="rfc.section.12.6"><a href="#rfc.section.12.6">12.6</a>&nbsp;<a href="#METHOD_BASELINE-CONTROL">BASELINE-CONTROL Method</a></h3><div id="rfc.section.12.6.p.1"><p>A
 collection can be placed under baseline control with a BASELINE-CONTROL
 request. When a collection is placed under baseline control, the 
DAV:version-controlled-configuration property of the collection is set 
to identify a new version-controlled configuration. This 
version-controlled configuration can be checked out and then checked in 
to create a new baseline for that collection.<a class="self" href="#rfc.section.12.6.p.1">¶</a></p></div><div id="rfc.section.12.6.p.2"><p>If
 a baseline is specified in the request body, the DAV:checked-in version
 of the new version-controlled configuration will be that baseline, and 
the collection is initialized to contain version-controlled members 
whose DAV:checked-in versions and relative names are determined by the 
specified baseline.<a class="self" href="#rfc.section.12.6.p.2">¶</a></p></div><div id="rfc.section.12.6.p.3"><p>If
 no baseline is specified, a new baseline history is created containing a
 baseline that captures the state of the version-controlled members of 
the collection, and the DAV:checked-in version of the version-controlled
 configuration will be that baseline.<a class="self" href="#rfc.section.12.6.p.3">¶</a></p></div><div id="rfc.section.12.6.p.4"><p><span id="rfc.iref.b.3"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.12.6.p.4">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:baseline-control XML element. <span id="rfc.figure.u.109"><pre class="inline">&lt;!ELEMENT baseline-control ANY&gt;
ANY value: A sequence of elements with at most one DAV:baseline
element.

&lt;!ELEMENT baseline (href)&gt;
</pre></span> </li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:baseline-control-response XML element. <span id="rfc.figure.u.110"><pre class="inline">&lt;!ELEMENT baseline-control-response ANY&gt;
</pre></span> </li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.12.6.p.5"><p><span id="rfc.iref.b.4"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.12.6.p.5">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.119"></span> <span id="rfc.iref.c.138"></span>
 (DAV:version-controlled-configuration-must-not-exist): The 
DAV:version-controlled-configuration property of the collection 
identified by the request-URL <em class="bcp14">MUST</em> not exist.</li><li><span id="rfc.iref.d.120"></span> <span id="rfc.iref.c.139"></span> (DAV:must-be-baseline): The DAV:href of the DAV:baseline element in the request body <em class="bcp14">MUST</em> identify a baseline.</li><li><span id="rfc.iref.d.121"></span> <span id="rfc.iref.c.140"></span>
 (DAV:must-have-no-version-controlled-members): If a DAV:baseline 
element is specified in the request body, the collection identified by 
the request-URL <em class="bcp14">MUST</em> have no version-controlled members.</li><li><span id="rfc.iref.d.122"></span> <span id="rfc.iref.c.141"></span>
 (DAV:one-baseline-controlled-collection-per-history-per-workspace): If 
the request-URL identifies a workspace or a member of a workspace, and 
if a baseline is specified in a DAV:baseline element in the request 
body, then there <em class="bcp14">MUST NOT</em> be another collection 
in that workspace whose DAV:version-controlled-configuration property 
identifies a version-controlled configuration for the baseline history 
of that baseline.</li></ul></div><div id="rfc.section.12.6.p.6"><p><span id="rfc.iref.b.5"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.12.6.p.6">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.123"></span> <span id="rfc.iref.c.142"></span>
 (DAV:create-version-controlled-configuration): A new version-controlled
 configuration is created, whose DAV:baseline-controlled-collection 
property identifies the collection.</li><li><span id="rfc.iref.d.124"></span> <span id="rfc.iref.c.143"></span>
 (DAV:reference-version-controlled-configuration): The 
DAV:version-controlled-configuration of the collection identifies the 
new version-controlled configuration.</li><li><span id="rfc.iref.d.125"></span> <span id="rfc.iref.c.144"></span>
 (DAV:select-existing-baseline): If the request body specifies a 
baseline, the DAV:checked-in property of the new version-controlled 
configuration <em class="bcp14">MUST</em> have been set to identify this
 baseline. A version-controlled member of the collection will be created
 for each version in the baseline, where the version-controlled member 
will have the content and dead properties of that version, and will have
 the same name relative to the collection as the corresponding 
version-controlled resource had when the baseline was created. Any 
nested collections that are needed to provide the appropriate name for a
 version-controlled member will be created.</li><li><span id="rfc.iref.d.126"></span> <span id="rfc.iref.c.145"></span> (DAV:create-new-baseline): If no baseline is specified in the request body, the request <em class="bcp14">MUST</em> have created a new baseline history at a server-defined URL, and <em class="bcp14">MUST</em> have created a new baseline in that baseline history. The DAV:baseline-collection of the new baseline <em class="bcp14">MUST</em>
 identify a collection whose members have the same relative name and 
DAV:checked-in version as the version-controlled members of the request 
collection. The DAV:checked-in property of the new version-controlled 
configuration <em class="bcp14">MUST</em> identify the new baseline.</li></ul></div><section id="n-example---baseline-control"><h4 id="rfc.section.12.6.1"><a href="#rfc.section.12.6.1">12.6.1</a>&nbsp;<a href="#n-example---baseline-control">Example - BASELINE-CONTROL</a></h4><div id="rfc.figure.u.111"><p>&gt;&gt;REQUEST</p><pre class="text2">BASELINE-CONTROL /src HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:baseline-control xmlns:D="DAV:"&gt;
  &lt;D:href&gt;http://www.webdav.org/repo/blh/13/ver/8&lt;/D:href&gt;
&lt;/D:baseline-control&gt;
</pre></div><div id="rfc.figure.u.112"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Cache-Control: no-cache
Content-Length: 0
</pre></div><div id="rfc.section.12.6.1.p.1"><p>In this example, the 
collection /src is placed under baseline control, and is populated with 
members from an existing baseline. A new version-controlled 
configuration (/repo/vcc/128) is created and associated with /src, and 
/src is initialized with version-controlled members whose DAV:checked-in
 versions are those selected by the DAV:baseline-collection 
(/repo/bc/15) of the specified baseline (/repo/blh/13/ver/8). The 
following diagram illustrates the resulting state on the server.<a class="self" href="#rfc.section.12.6.1.p.1">¶</a></p></div><div id="rfc.figure.u.113"><pre class="drawing">         ┌─────────────────────────────────────┐
         │Baseline-Controlled Collection       │&lt;------+
         │/src                                 │       |
         ├─────────────────────────────────────┤       |
         │DAV:version-controlled-configuration │---+   |
         └─────────────────────────────────────┘   |   |
                                                   |   |
                                                   |   |
         ┌─────────────────────────────────────┐   |   |
         │Version-Controlled Configuration     │&lt;--+   |
         │/repo/vcc/128                        │       |
         ├─────────────────────────────────────┤       |
         │DAV:baseline-controlled-collection   │-------+
         ├─────────────────────────────────────┤
         │DAV:checked-in                       │-------+
         ├─────────────────────────────────────┤       |
         │DAV:version-history                  │---+   |
         └─────────────────────────────────────┘   |   |
                                                   |   |
                                                   |   |
         ┌────────────────────────┐                |   |
         │Baseline History        │&lt;---------------+   |
         │/repo/blh/13            │                    |
         ├────────────────────────┤                    |
         │DAV:version-set         │----------------+   |
         └────────────────────────┘    |   |   |   |   |
                                       v   |   v   v   |
                                           |           |
         ┌────────────────────────┐        |           |
         │Baseline                │&lt;-------+-----------+
         │/repo/blh/13/ver/8      │
         ├────────────────────────┤     ┌──────────────┐
         │DAV:baseline-collection │----&gt;│Collection    │
         └────────────────────────┘     │/repo/bc/15   │
                                        └──────────────┘
</pre></div><div id="rfc.section.12.6.1.p.2"><p>In order to create new 
baselines of /src, /repo/vcc/128 can be checked out, new versions can be
 created or selected by the version-controlled members of /src, and then
 /repo/vcc/128 can be checked in to capture the current state of those 
version-controlled members.<a class="self" href="#rfc.section.12.6.1.p.2">¶</a></p></div></section></section><section id="n-dav-compare-baseline-report"><h3 id="rfc.section.12.7"><a href="#rfc.section.12.7">12.7</a>&nbsp;<a href="#n-dav-compare-baseline-report">DAV:compare-baseline Report</a></h3><div id="rfc.section.12.7.p.1"><p>A
 DAV:compare-baseline report contains the differences between the 
baseline identified by the request-URL (the "request baseline") and the 
baseline specified in the request body (the "compare baseline").<a class="self" href="#rfc.section.12.7.p.1">¶</a></p></div><div id="rfc.section.12.7.p.2"><p><span id="rfc.iref.d.127"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.12.7.p.2">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:compare-baseline XML element. <span id="rfc.figure.u.114"><pre class="inline">&lt;!ELEMENT compare-baseline (href)&gt;
</pre></span> </li><li>The response body for a successful request <em class="bcp14">MUST</em> be a DAV:compare-baseline-report XML element. <span id="rfc.figure.u.115"><pre class="inline">&lt;!ELEMENT compare-baseline-report
(added-version | deleted-version | changed-version)*&gt;
</pre></span> </li><li>A DAV:added-version element identifies a version 
that is the DAV:checked-in version of a member of the 
DAV:baseline-collection of the compare baseline, but no version in the 
version history of that version is the DAV:checked-in version of a 
member of the DAV:baseline-collection of the request baseline. <span id="rfc.figure.u.116"><pre class="inline">&lt;!ELEMENT added-version (href)&gt;
</pre></span> </li><li>A DAV:deleted-version element identifies a 
version that is the DAV:checked-in version of a member of the 
DAV:baseline-collection of the request baseline, but no version in the 
version history of that version is the DAV:checked-in version of a 
member of the DAV:baseline-collection of the compare baseline. <span id="rfc.figure.u.117"><pre class="inline">&lt;!ELEMENT deleted-version (href)&gt;
</pre></span> </li><li>A DAV:changed-version element identifies two 
different versions from the same version history that are the 
DAV:checked-in version of the DAV:baseline-collection of the request 
baseline and the compare baseline, respectively. <span id="rfc.figure.u.118"><pre class="inline">&lt;!ELEMENT changed-version (href, href)&gt;
</pre></span> </li></ul></div><div id="rfc.section.12.7.p.3"><p><span id="rfc.iref.d.128"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.12.7.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.129"></span> <span id="rfc.iref.c.146"></span> (DAV:must-be-baseline): The DAV:href in the request body <em class="bcp14">MUST</em> identify a baseline.</li><li><span id="rfc.iref.d.130"></span> <span id="rfc.iref.c.147"></span> (DAV:baselines-from-same-history): A server <em class="bcp14">MAY</em> require that the baselines being compared be from the same baseline history.</li></ul></div><section id="n-example---dav-compare-baseline-report"><h4 id="rfc.section.12.7.1"><a href="#rfc.section.12.7.1">12.7.1</a>&nbsp;<a href="#n-example---dav-compare-baseline-report">Example - DAV:compare-baseline Report</a></h4><div id="rfc.figure.u.119"><p>&gt;&gt;REQUEST</p><pre class="text2">REPORT /bl-his/12/bl/14 HTTP/1.1
Host: repo.webdav.com
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:compare-baseline xmlns:D="DAV:"&gt;
  &lt;D:href&gt;http://repo.webdav.org/bl-his/12/bl/15&lt;/D:href&gt;
&lt;/D:compare-baseline&gt;
</pre></div><div id="rfc.figure.u.120"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:compare-baseline-report xmlns:D="DAV:"&gt;
  &lt;D:added-version&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/23/ver/8&lt;/D:href&gt;
  &lt;/D:added-version&gt;
  &lt;D:changed-version&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/29/ver/12&lt;/D:href&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/29/ver/19&lt;/D:href&gt;
  &lt;/D:changed-version&gt;
  &lt;D:deleted-version&gt;
    &lt;D:href&gt;http://repo.webdav.org/his/12/ver/4&lt;/D:href&gt;
  &lt;/D:deleted-version&gt;
&lt;/D:compare-baseline-report&gt;
</pre></div><div id="rfc.section.12.7.1.p.1"><p>In this example, the differences between baseline 14 and baseline 15 of http://repo.webdav.org/bl-his/12 are identified.<a class="self" href="#rfc.section.12.7.1.p.1">¶</a></p></div></section></section><section id="n-additional-options-semantics_8"><h3 id="rfc.section.12.8"><a href="#rfc.section.12.8">12.8</a>&nbsp;<a href="#n-additional-options-semantics_8">Additional OPTIONS Semantics</a></h3><div id="rfc.section.12.8.p.1"><p>If a server supports the baseline feature, it <em class="bcp14">MUST</em>
 include "baseline" as a field in the DAV response header from an 
OPTIONS request on any resource that supports any versioning properties,
 reports, or methods.<a class="self" href="#rfc.section.12.8.p.1">¶</a></p></div></section><section id="n-additional-mkcol-semantics_1"><h3 id="rfc.section.12.9"><a href="#rfc.section.12.9">12.9</a>&nbsp;<a href="#n-additional-mkcol-semantics_1">Additional MKCOL Semantics</a></h3><div id="rfc.section.12.9.p.1"><p><span id="rfc.iref.m.14"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.12.9.p.1">¶</a></p><ul class="empty"><li>If
 a server automatically puts a newly created collection under baseline 
control, all postconditions for BASELINE-CONTROL apply to the MKCOL.</li></ul></div></section><section id="n-additional-copy-semantics_5"><h3 id="rfc.section.12.10"><a href="#rfc.section.12.10">12.10</a>&nbsp;<a href="#n-additional-copy-semantics_5">Additional COPY Semantics</a></h3><div id="rfc.section.12.10.p.1"><p><span id="rfc.iref.c.148"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.12.10.p.1">¶</a></p><ul class="empty"><li>If
 the request creates a new collection at the Destination, and a server 
automatically puts a newly created collection under baseline control, 
all postconditions for BASELINE-CONTROL apply to the COPY.</li></ul></div></section><section id="n-additional-checkout-semantics_2"><h3 id="rfc.section.12.11"><a href="#rfc.section.12.11">12.11</a>&nbsp;<a href="#n-additional-checkout-semantics_2">Additional CHECKOUT Semantics</a></h3><div id="rfc.section.12.11.p.1"><p><span id="rfc.iref.c.149"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.12.11.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.131"></span> <span id="rfc.iref.c.150"></span>
 (DAV:must-not-update-baseline-collection): If the request-URL 
identifies a member of the configuration rooted at the 
DAV:baseline-collection of a baseline, the request <em class="bcp14">MUST</em> fail.</li></ul></div></section><section id="n-additional-checkin-semantics_3"><h3 id="rfc.section.12.12"><a href="#rfc.section.12.12">12.12</a>&nbsp;<a href="#n-additional-checkin-semantics_3">Additional CHECKIN Semantics</a></h3><div id="rfc.section.12.12.p.1"><p><span id="rfc.iref.c.151"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.12.12.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.132"></span> <span id="rfc.iref.c.152"></span>
 (DAV:no-checked-out-baseline-controlled-collection-members): If the 
request-URL identifies a version-controlled configuration, all 
version-controlled members of the DAV:baseline-controlled-collection of 
the version-controlled configuration <em class="bcp14">MUST</em> be checked-in.</li><li><span id="rfc.iref.d.133"></span> <span id="rfc.iref.c.153"></span>
 (DAV:one-version-per-history-per-baseline): If the request-URL 
identifies a version-controlled configuration, the set of versions 
selected by that version-controlled configuration <em class="bcp14">MUST</em>
 contain at most one version from any version history, where a version 
is selected by a version-controlled configuration if the version is 
identified by the DAV:checked-in property of any member of the 
configuration rooted at the DAV:baseline-controlled collection of that 
version-controlled configuration, or is identified by the DAV:checked-in
 property of any member of the configuration rooted at the 
DAV:baseline-collection of any subbaseline of that version-controlled 
configuration.</li><li><span id="rfc.iref.d.134"></span> <span id="rfc.iref.c.154"></span>
 (DAV:cannot-modify-version-controlled-configuration): If the 
request-URL identifies a version-controlled member of a 
baseline-controlled collection whose version-controlled configuration is
 checked-in, the request <em class="bcp14">MUST</em> fail unless the 
DAV:auto-version property of the version-controlled configuration will 
automatically check out that version-controlled configuration when it is
 modified.</li></ul></div><div id="rfc.section.12.12.p.2"><p><span id="rfc.iref.c.155"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.12.12.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.135"></span> <span id="rfc.iref.c.156"></span>
 (DAV:create-baseline-collection): If the request-URL identifies a 
version-controlled configuration, the DAV:baseline-collection of the new
 baseline identifies a collection whose members have the same relative 
name and DAV:checked-in version as the members of the 
DAV:baseline-controlled-collection of the version-controlled 
configuration at the time of the request.</li><li><span id="rfc.iref.d.136"></span> <span id="rfc.iref.c.157"></span>
 (DAV:modify-configuration): If the request-URL identifies a 
version-controlled member of a baseline-controlled collection, this is a
 modification to the version-controlled configuration of that 
baseline-controlled collection, and standard auto-versioning semantics 
apply.</li></ul></div></section><section id="additional.update.semantics.with.baseline.feature"><h3 id="rfc.section.12.13"><a href="#rfc.section.12.13">12.13</a>&nbsp;<a href="#additional.update.semantics.with.baseline.feature">Additional UPDATE Semantics</a></h3><div id="rfc.section.12.13.p.1"><p><span id="rfc.iref.u.11"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.12.13.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.137"></span> <span id="rfc.iref.c.158"></span>
 (DAV:baseline-controlled-members-must-be-checked-in): If the 
request-URL identifies a version-controlled configuration, then all 
version-controlled members of the DAV:baseline-controlled-collection of 
that version-controlled configuration <em class="bcp14">MUST</em> be checked-in.</li><li><span id="rfc.iref.d.138"></span> <span id="rfc.iref.c.159"></span>
 (DAV:must-not-update-baseline-collection): If the request-URL 
identifies a member of the configuration rooted at the 
DAV:baseline-collection of a baseline, the request <em class="bcp14">MUST</em> fail.</li><li><span id="rfc.iref.d.139"></span> <span id="rfc.iref.c.160"></span>
 (DAV:cannot-modify-version-controlled-configuration): If the request 
updates the DAV:checked-in property of any version-controlled member of a
 baseline-controlled collection whose version-controlled configuration 
is checked-in, the request <em class="bcp14">MUST</em> fail unless the 
DAV:auto-version property of the version-controlled configuration will 
automatically check out that version-controlled configuration when it is
 modified.</li></ul></div><div id="rfc.section.12.13.p.2"><p><span id="rfc.iref.u.12"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.12.13.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.140"></span> <span id="rfc.iref.c.161"></span>
 (DAV:set-baseline-controlled-collection-members): If the request 
updated the DAV:checked-in property of a version-controlled 
configuration, then the version-controlled members of the 
DAV:baseline-controlled-collection of that version-controlled 
configuration <em class="bcp14">MUST</em> have been updated so that they
 have the same relative name, content, and dead properties as the 
members of the DAV:baseline-collection of the baseline. In particular: <ul><li>A version-controlled member for a given version history <em class="bcp14">MUST</em>
 have been deleted if there is no version-controlled member for that 
version history in the DAV:baseline-collection of the baseline.</li><li>A version-controlled member for a given version history <em class="bcp14">MUST</em>
 have been renamed if its name relative to the baseline-controlled 
collection is different from that of the version-controlled member for 
that version history in the DAV:baseline-collection of the baseline.</li><li>A new version-controlled member <em class="bcp14">MUST</em>
 have been created for each member of the DAV:baseline-collection of the
 baseline for which there is no corresponding version-controlled member 
in the baseline-controlled collection.</li><li>An UPDATE request <em class="bcp14">MUST</em>
 have been applied to each version-controlled member for a given version
 history whose DAV:checked-in version is not the same as that of the 
version-controlled member for that version history in the 
DAV:baseline-collection of the baseline.</li></ul> </li><li><span id="rfc.iref.d.141"></span> <span id="rfc.iref.c.162"></span>
 (DAV:update-subbaselines): If the request updated a version-controlled 
configuration whose DAV:baseline-controlled-collection contains a 
baseline-controlled member for one of the subbaselines of the request 
baseline, then the DAV:checked-in property of the version-controlled 
configuration of that baseline-controlled member <em class="bcp14">MUST</em>
 have been updated to be that subbaseline. If the request updated a 
version-controlled configuration whose 
DAV:baseline-controlled-collection is a member of a workspace that 
contains a baseline-controlled member for one of the subbaselines of the
 request baseline, then the DAV:checked-in property of the 
version-controlled configuration of that baseline-controlled member <em class="bcp14">MUST</em> have been updated to be that subbaseline.</li><li><span id="rfc.iref.d.142"></span> <span id="rfc.iref.c.163"></span>
 (DAV:modify-configuration): If the request updated the DAV:checked-in 
property of any version-controlled member of a baseline-controlled 
collection, and if this DAV:checked-in property differs from the 
DAV:checked-in property of the corresponding version-controlled member 
of the DAV:baseline-collection of the DAV:checked-in baseline of the 
DAV:version-controlled-configuration of the baseline-controlled 
collection, then this is a modification to that version-controlled 
configuration, and standard auto-versioning semantics apply.</li></ul></div></section><section id="n-additional-merge-semantics_1"><h3 id="rfc.section.12.14"><a href="#rfc.section.12.14">12.14</a>&nbsp;<a href="#n-additional-merge-semantics_1">Additional MERGE Semantics</a></h3><div id="rfc.section.12.14.p.1"><p>If
 the merge source is a baseline, the merge target is a 
version-controlled configuration for the baseline history of that 
baseline, where the baseline-controlled collection of that 
version-controlled configuration is a member of the collection 
identified by the request-URL.<a class="self" href="#rfc.section.12.14.p.1">¶</a></p></div><div id="rfc.section.12.14.p.2"><p><span id="rfc.iref.m.15"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.12.14.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.143"></span> <span id="rfc.iref.c.164"></span> (DAV:must-not-update-baseline-collection): Same semantics as UPDATE (<a href="#additional.update.semantics.with.baseline.feature" title="Additional UPDATE Semantics">Section&nbsp;12.13</a>).</li><li><span id="rfc.iref.d.144"></span> <span id="rfc.iref.c.165"></span> (DAV:cannot-modify-version-controlled-configuration): Same semantics as UPDATE (<a href="#additional.update.semantics.with.baseline.feature" title="Additional UPDATE Semantics">Section&nbsp;12.13</a>).</li></ul></div><div id="rfc.section.12.14.p.3"><p><span id="rfc.iref.m.16"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.12.14.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.145"></span> <span id="rfc.iref.c.166"></span>
 (DAV:merge-baseline): If the merge target is a version-controlled 
configuration whose DAV:checked-out baseline is not a descendant of the 
merge baseline, then the merge baseline <em class="bcp14">MUST</em> have
 been added to the DAV:auto-merge-set of a version-controlled 
configuration. The DAV:checked-in version of each member of the 
DAV:baseline-collection of that baseline <em class="bcp14">MUST</em> have been merged into the DAV:baseline-controlled-collection of that version-controlled configuration.</li><li><span id="rfc.iref.d.146"></span> <span id="rfc.iref.c.167"></span>
 (DAV:merge-subbaselines): If the merge target is a version-controlled 
configuration whose DAV:baseline-controlled-collection contains a 
baseline-controlled member for one of the subbaselines of the merge 
baseline, then that subbaseline <em class="bcp14">MUST</em> have been 
merged into the version-controlled configuration of that 
baseline-controlled member. If the merge target is a version-controlled 
configuration whose DAV:baseline-controlled-collection is a member of a 
workspace that contains a baseline-controlled member for one of the 
subbaselines of the merge baseline, then that subbaseline <em class="bcp14">MUST</em> have been merged into the version-controlled configuration of that baseline-controlled member.</li><li><span id="rfc.iref.d.147"></span> <span id="rfc.iref.c.168"></span> (DAV:set-baseline-controlled-collection-members): Same semantics as UPDATE (<a href="#additional.update.semantics.with.baseline.feature" title="Additional UPDATE Semantics">Section&nbsp;12.13</a>).</li><li><span id="rfc.iref.d.148"></span> <span id="rfc.iref.c.169"></span> (DAV:modify-configuration): Same semantics as UPDATE (see <a href="#additional.update.semantics.with.baseline.feature" title="Additional UPDATE Semantics">Section&nbsp;12.13</a>).</li></ul></div></section></section><hr class="noprint"><section id="activity.feature"><h2 id="rfc.section.13" class="np"><a href="#rfc.section.13">13.</a>&nbsp;<a href="#activity.feature">Activity Feature</a></h2><div id="rfc.section.13.p.1"><p>An
 activity is a resource that selects a set of versions that are on a 
single "line of descent", where a line of descent is a sequence of 
versions connected by successor relationships. If an activity selects 
versions from multiple version histories, the versions selected in each 
version history must be on a single line of descent.<a class="self" href="#rfc.section.13.p.1">¶</a></p></div><div id="rfc.section.13.p.2"><p>A
 common problem that motivates the use of activities is that it is often
 desirable to perform several different logical changes in a single 
workspace, and then selectively merge a subset of those logical changes 
to other workspaces. An activity can be used to represent a single 
logical change, where an activity tracks all the resources that were 
modified to effect that single logical change. When a version-controlled
 resource is checked out, the user specifies which activity should be 
associated with a new version that will be created when that 
version-controlled resource is checked in. It is then possible to select
 a particular logical change for merging into another workspace, by 
specifying the appropriate activity in a MERGE request.<a class="self" href="#rfc.section.13.p.2">¶</a></p></div><div id="rfc.section.13.p.3"><p>Another
 common problem is that although a version-controlled resource may need 
to have multiple lines of descent, all work done by members of a given 
team must be on a single line of descent (to avoid merging between team 
members). An activity resource provides the mechanism for addressing 
this problem. When a version-controlled resource is checked out, a 
client can request that an existing activity be used or that a new 
activity be created. Activity semantics then ensure that all versions in
 a given version history that are associated with an activity are on a 
single line of descent. If all members of a team share a common activity
 (or sub-activities of a common activity), then all changes made by 
members of that team will be on a single line of descent.<a class="self" href="#rfc.section.13.p.3">¶</a></p></div><div id="rfc.section.13.p.4"><p>The
 following diagram illustrates activities. Version V5 is the latest 
version of foo.html selected by activity Act-2, and version V8 is the 
latest version of bar.html selected by activity Act-2.<a class="self" href="#rfc.section.13.p.4">¶</a></p></div><div id="rfc.figure.u.121"><pre class="drawing">                  foo.html History       bar.html History

                        ┌───┐                  ┌───┐
                   Act-1│   │V1           Act-1│   │V6
                        └───┘                  └───┘
                          |                      |
                          |                      |
                        ┌───┐                  ┌───┐
                   Act-1│   │V2           Act-2│   │V7
                        └───┘                  └───┘
                       /     \                   |
                      /       \                  |
                 ┌───┐         ┌───┐           ┌───┐
            Act-1│   │V3  Act-2│   │V4    Act-2│   │V8
                 └───┘         └───┘           └───┘
                                 |               |
                                 |               |
                               ┌───┐           ┌───┐
                          Act-2│   │V5    Act-3│   │V9
                               └───┘           └───┘
</pre></div><div id="rfc.section.13.p.5"><p>Activities appear under a 
variety of names in existing versioning systems. When an activity is 
used to capture a logical change, it is commonly called a "change set". 
When an activity is used to capture a line of descent, it is commonly 
called a "branch". When a system supports both branches and change sets,
 it is often useful to require that a particular change set occur on a 
particular branch. This relationship can be captured by making the 
change set activity be a "subactivity" of the branch activity.<a class="self" href="#rfc.section.13.p.5">¶</a></p></div><section id="n-activity-properties"><h3 id="rfc.section.13.1"><a href="#rfc.section.13.1">13.1</a>&nbsp;<a href="#n-activity-properties">Activity Properties</a></h3><div id="rfc.section.13.1.p.1"><p>The DAV:resourcetype of an activity <em class="bcp14">MUST</em> be DAV:activity.<a class="self" href="#rfc.section.13.1.p.1">¶</a></p></div><div id="rfc.section.13.1.p.2"><p>The activity feature introduces the following <em class="bcp14">REQUIRED</em> properties for an activity.<a class="self" href="#rfc.section.13.1.p.2">¶</a></p></div><section id="PROPERTY_activity-version-set"><h4 id="rfc.section.13.1.1"><a href="#rfc.section.13.1.1">13.1.1</a>&nbsp;<a href="#PROPERTY_activity-version-set">DAV:activity-version-set (computed)</a></h4><div id="rfc.section.13.1.1.p.1"><p>This
 property identifies each version whose DAV:activity-set property 
identifies this activity. Multiple versions of a single version history 
can be selected by an activity's DAV:activity-version-set property, but 
all DAV:activity-version-set versions from a given version history must 
be on a single line of descent from the root version of that version 
history. <a class="self" href="#rfc.section.13.1.1.p.1">¶</a></p><span id="rfc.figure.u.122"><pre class="inline">&lt;!ELEMENT activity-version-set (href*)&gt;
</pre></span></div></section><section id="PROPERTY_activity-checkout-set"><h4 id="rfc.section.13.1.2"><a href="#rfc.section.13.1.2">13.1.2</a>&nbsp;<a href="#PROPERTY_activity-checkout-set">DAV:activity-checkout-set (computed)</a></h4><div id="rfc.section.13.1.2.p.1"><p>This property identifies each checked-out resource whose DAV:activity-set identifies this activity. <a class="self" href="#rfc.section.13.1.2.p.1">¶</a></p><span id="rfc.figure.u.123"><pre class="inline">&lt;!ELEMENT activity-checkout-set (href*)&gt;
</pre></span></div></section><section id="PROPERTY_subactivity-set"><h4 id="rfc.section.13.1.3"><a href="#rfc.section.13.1.3">13.1.3</a>&nbsp;<a href="#PROPERTY_subactivity-set">DAV:subactivity-set</a></h4><div id="rfc.section.13.1.3.p.1"><p>This
 property identifies each activity that forms a part of the logical 
change being captured by this activity. An activity behaves as if its 
DAV:activity-version-set is extended by the DAV:activity-version-set of 
each activity identified in the DAV:subactivity-set. In particular, the 
versions in this extended set <em class="bcp14">MUST</em> be on a single
 line of descent, and when an activity selects a version for merging, 
the latest version in this extended set is the one that will be merged.<a class="self" href="#rfc.section.13.1.3.p.1">¶</a></p></div><div id="rfc.section.13.1.3.p.2"><p>A server <em class="bcp14">MAY</em> reject attempts to modify the DAV:subactivity-set of an activity. <a class="self" href="#rfc.section.13.1.3.p.2">¶</a></p><span id="rfc.figure.u.124"><pre class="inline">&lt;!ELEMENT subactivity-set (href*)&gt;
</pre></span></div></section><section id="PROPERTY_current-workspace-set"><h4 id="rfc.section.13.1.4"><a href="#rfc.section.13.1.4">13.1.4</a>&nbsp;<a href="#PROPERTY_current-workspace-set">DAV:current-workspace-set (computed)</a></h4><div id="rfc.section.13.1.4.p.1"><p>This property identifies each workspace whose DAV:current-activity-set identifies this activity. <a class="self" href="#rfc.section.13.1.4.p.1">¶</a></p><span id="rfc.figure.u.125"><pre class="inline">&lt;!ELEMENT current-workspace-set (href*)&gt;
</pre></span></div></section></section><section id="n-additional-version-properties_5"><h3 id="rfc.section.13.2"><a href="#rfc.section.13.2">13.2</a>&nbsp;<a href="#n-additional-version-properties_5">Additional Version Properties</a></h3><div id="rfc.section.13.2.p.1"><p>The activity feature introduces the following <em class="bcp14">REQUIRED</em> property for a version.<a class="self" href="#rfc.section.13.2.p.1">¶</a></p></div><section id="PROPERTY_activity-set"><h4 id="rfc.section.13.2.1"><a href="#rfc.section.13.2.1">13.2.1</a>&nbsp;<a href="#PROPERTY_activity-set">DAV:activity-set</a></h4><div id="rfc.section.13.2.1.p.1"><p>This
 property identifies the activities that determine to which logical 
changes this version contributes, and on which lines of descent this 
version appears. A server <em class="bcp14">MAY</em> restrict the DAV:activity-set to identify a single activity. A server <em class="bcp14">MAY</em> refuse to allow the value of the DAV:activity-set property of a version to be modified. <a class="self" href="#rfc.section.13.2.1.p.1">¶</a></p><span id="rfc.figure.u.126"><pre class="inline">&lt;!ELEMENT activity-set (href*)&gt;
</pre></span></div></section></section><section id="n-additional-checked-out-resource-properties_2"><h3 id="rfc.section.13.3"><a href="#rfc.section.13.3">13.3</a>&nbsp;<a href="#n-additional-checked-out-resource-properties_2">Additional Checked-Out Resource Properties</a></h3><div id="rfc.section.13.3.p.1"><p>The activity feature introduces the following <em class="bcp14">REQUIRED</em> properties for a checked-out resource.<a class="self" href="#rfc.section.13.3.p.1">¶</a></p></div><section id="PROPERTY_unreserved"><h4 id="rfc.section.13.3.1"><a href="#rfc.section.13.3.1">13.3.1</a>&nbsp;<a href="#PROPERTY_unreserved">DAV:unreserved</a></h4><div id="rfc.section.13.3.1.p.1"><p>This
 property of a checked-out resource indicates whether the 
DAV:activity-set of another checked-out resource associated with the 
version history of this version-controlled resource can have an activity
 that is in the DAV:activity-set property of this checked-out resource.<a class="self" href="#rfc.section.13.3.1.p.1">¶</a></p></div><div id="rfc.section.13.3.1.p.2"><p>A
 result of the requirement that an activity must form a single line of 
descent through a given version history is that if multiple checked-out 
resources for a given version history are checked out unreserved into a 
single activity, only the first CHECKIN will succeed. Before another of 
these checked-out resources can be checked in, the user will first have 
to merge into that checked-out resource the latest version selected by 
that activity from that version history, and then modify the 
DAV:predecessor-set of that checked-out resource to identify that 
version. <a class="self" href="#rfc.section.13.3.1.p.2">¶</a></p><span id="rfc.figure.u.127"><pre class="inline">&lt;!ELEMENT unreserved (#PCDATA)&gt;
PCDATA value: boolean
</pre></span></div></section><section id="n-dav-activity-set"><h4 id="rfc.section.13.3.2"><a href="#rfc.section.13.3.2">13.3.2</a>&nbsp;<a href="#n-dav-activity-set">DAV:activity-set</a></h4><div id="rfc.section.13.3.2.p.1"><p>This
 property of a checked-out resource determines the DAV:activity-set 
property of the version that results from checking in this resource.<a class="self" href="#rfc.section.13.3.2.p.1">¶</a></p></div></section></section><section id="n-additional-workspace-properties_2"><h3 id="rfc.section.13.4"><a href="#rfc.section.13.4">13.4</a>&nbsp;<a href="#n-additional-workspace-properties_2">Additional Workspace Properties</a></h3><div id="rfc.section.13.4.p.1"><p>The activity feature introduces the following <em class="bcp14">REQUIRED</em> property for a workspace.<a class="self" href="#rfc.section.13.4.p.1">¶</a></p></div><section id="PROPERTY_current-activity-set"><h4 id="rfc.section.13.4.1"><a href="#rfc.section.13.4.1">13.4.1</a>&nbsp;<a href="#PROPERTY_current-activity-set">DAV:current-activity-set</a></h4><div id="rfc.section.13.4.1.p.1"><p>This
 property identifies the activities that currently are being performed 
in this workspace. When a member of this workspace is checked out, if no
 activity is specified in the checkout request, the 
DAV:current-activity-set will be used. This allows an activity-unaware 
client to update a workspace in which activity tracking is required. The
 DAV:current-activity-set <em class="bcp14">MAY</em> be restricted to identify at most one activity. <a class="self" href="#rfc.section.13.4.1.p.1">¶</a></p><span id="rfc.figure.u.128"><pre class="inline">&lt;!ELEMENT current-activity-set (href*)&gt;
</pre></span></div></section></section><section id="METHOD_MKACTIVITY"><h3 id="rfc.section.13.5"><a href="#rfc.section.13.5">13.5</a>&nbsp;<a href="#METHOD_MKACTIVITY">MKACTIVITY Method</a></h3><div id="rfc.section.13.5.p.1"><p>A MKACTIVITY request creates a new activity resource. A server <em class="bcp14">MAY</em>
 restrict activity creation to particular collections, but a client can 
determine the location of these collections from a 
DAV:activity-collection-set OPTIONS request.<a class="self" href="#rfc.section.13.5.p.1">¶</a></p></div><div id="rfc.section.13.5.p.2"><p><span id="rfc.iref.m.17"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.13.5.p.2">¶</a></p><ul class="empty"><li>If a request body is included, it <em class="bcp14">MUST</em> be a DAV:mkactivity XML element. <span id="rfc.figure.u.129"><pre class="inline">&lt;!ELEMENT mkactivity ANY&gt;
</pre></span></li><li>If a response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:mkactivity-response XML element. <span id="rfc.figure.u.130"><pre class="inline">&lt;!ELEMENT mkactivity-response ANY&gt;
</pre></span></li><li>The response <em class="bcp14">MUST</em> include a Cache-Control:no-cache header.</li></ul></div><div id="rfc.section.13.5.p.3"><p><span id="rfc.iref.m.18"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.13.5.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.149"></span> <span id="rfc.iref.c.170"></span> (DAV:resource-must-be-null): A resource <em class="bcp14">MUST NOT</em> exist at the request-URL.</li><li><span id="rfc.iref.d.150"></span> <span id="rfc.iref.c.171"></span> (DAV:activity-location-ok): The request-URL <em class="bcp14">MUST</em> identify a location where an activity can be created.</li></ul></div><div id="rfc.section.13.5.p.4"><p><span id="rfc.iref.m.19"></span> <b>Postconditions:</b> <a class="self" href="#rfc.section.13.5.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.151"></span> <span id="rfc.iref.c.172"></span> (DAV:initialize-activity): A new activity exists at the request-URL. The DAV:resourcetype of the activity <em class="bcp14">MUST</em> be DAV:activity.</li></ul></div><section id="n-example---mkactivity"><h4 id="rfc.section.13.5.1"><a href="#rfc.section.13.5.1">13.5.1</a>&nbsp;<a href="#n-example---mkactivity">Example - MKACTIVITY</a></h4><div id="rfc.figure.u.131"><p>&gt;&gt;REQUEST</p><pre class="text2">MKACTIVITY /act/test-23 HTTP/1.1
Host: repo.webdav.org
Content-Length: 0
</pre></div><div id="rfc.figure.u.132"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 201 Created
Cache-Control: no-cache
</pre></div><div id="rfc.section.13.5.1.p.1"><p>In this example, a new activity is created at http://repo.webdav.org/act/test-23.<a class="self" href="#rfc.section.13.5.1.p.1">¶</a></p></div></section></section><section id="n-dav-latest-activity-version-report"><h3 id="rfc.section.13.6"><a href="#rfc.section.13.6">13.6</a>&nbsp;<a href="#n-dav-latest-activity-version-report">DAV:latest-activity-version Report</a></h3><div id="rfc.section.13.6.p.1"><p>The
 DAV:latest-activity-version report can be applied to a version history 
to identify the latest version that is selected from that version 
history by a given activity.<a class="self" href="#rfc.section.13.6.p.1">¶</a></p></div><div id="rfc.section.13.6.p.2"><p><span id="rfc.iref.d.152"></span> <b>Marshalling:</b> <a class="self" href="#rfc.section.13.6.p.2">¶</a></p><ul class="empty"><li>The request body <em class="bcp14">MUST</em> be a DAV:latest-activity-version XML element. <span id="rfc.figure.u.133"><pre class="inline">&lt;!ELEMENT latest-activity-version (href)&gt;
</pre></span></li><li>The response body for a successful request <em class="bcp14">MUST</em> be a DAV:latest-activity-version-report XML element. <span id="rfc.figure.u.134"><pre class="inline">&lt;!ELEMENT latest-activity-version-report (href)&gt;
</pre></span></li><li>The DAV:href of the response body <em class="bcp14">MUST</em>
 identify the version of the given version history that is a member of 
the DAV:activity-version-set of the given activity and has no descendant
 that is a member of the DAV:activity-version-set of that activity.</li></ul></div><div id="rfc.section.13.6.p.3"><p><span id="rfc.iref.d.153"></span> <b>Preconditions:</b> <a class="self" href="#rfc.section.13.6.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.154"></span> <span id="rfc.iref.c.173"></span> (DAV:must-be-activity): The DAV:href in the request body <em class="bcp14">MUST</em> identify an activity.</li></ul></div></section><section id="n-additional-options-semantics_9"><h3 id="rfc.section.13.7"><a href="#rfc.section.13.7">13.7</a>&nbsp;<a href="#n-additional-options-semantics_9">Additional OPTIONS Semantics</a></h3><div id="rfc.section.13.7.p.1"><p>If the server supports the activity feature, it <em class="bcp14">MUST</em>
 include "activity" as a field in the DAV response header from an 
OPTIONS request on any resource that supports any versioning properties,
 reports, or methods.<a class="self" href="#rfc.section.13.7.p.1">¶</a></p></div><div id="rfc.section.13.7.p.2"><p>A DAV:activity-collection-set element <em class="bcp14">MAY</em> be included in the request body to identify collections that may contain activity resources.<a class="self" href="#rfc.section.13.7.p.2">¶</a></p></div><div id="rfc.section.13.7.p.3"><p><span id="rfc.iref.o.3"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.13.7.p.3">¶</a></p><ul class="empty"><li>If an XML request body is included, it <em class="bcp14">MUST</em> be a DAV:options XML element. <span id="rfc.figure.u.135"><pre class="inline">&lt;!ELEMENT options ANY&gt;
ANY value: A sequence of elements with at most one
DAV:activity-collection-set element.
</pre></span></li><li>If an XML response body for a successful request is included, it <em class="bcp14">MUST</em> be a DAV:options-response XML element. <span id="rfc.figure.u.136"><pre class="inline">&lt;!ELEMENT options-response ANY&gt;
ANY value: A sequence of elements with at most one
DAV:activity-collection-set element.

&lt;!ELEMENT activity-collection-set (href*)&gt;
</pre></span></li><li>If DAV:activity-collection-set is included in the request body, the response body for a successful request <em class="bcp14">MUST</em> contain a DAV:activity-collection-set element identifying collections that may contain activities. An identified collection <em class="bcp14">MAY</em>
 be the root collection of a tree of collections, all of which may 
contain activities. Since different servers can control different parts 
of the URL namespace, different resources on the same host <em class="bcp14">MAY</em> have different DAV:activity-collection-set values. The identified collections <em class="bcp14">MAY</em> be located on different hosts from the resource.</li></ul></div></section><section id="n-additional-delete-semantics_4"><h3 id="rfc.section.13.8"><a href="#rfc.section.13.8">13.8</a>&nbsp;<a href="#n-additional-delete-semantics_4">Additional DELETE Semantics</a></h3><div id="rfc.section.13.8.p.1"><p><span id="rfc.iref.d.155"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.13.8.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.156"></span> <span id="rfc.iref.c.174"></span>
 (DAV:delete-activity-reference): If an activity is deleted, any 
reference to that activity in a DAV:activity-set, DAV:subactivity-set, 
or DAV:current-activity-set <em class="bcp14">MUST</em> be removed.</li></ul></div></section><section id="n-additional-move-semantics_5"><h3 id="rfc.section.13.9"><a href="#rfc.section.13.9">13.9</a>&nbsp;<a href="#n-additional-move-semantics_5">Additional MOVE Semantics</a></h3><div id="rfc.section.13.9.p.1"><p><span id="rfc.iref.m.20"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.13.9.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.157"></span> <span id="rfc.iref.c.175"></span>
 (DAV:update-checked-out-reference): If a checked-out resource is moved,
 any reference to that resource in a DAV:activity-checkout-set property <em class="bcp14">MUST</em> be updated to refer to the new location of that resource.</li><li><span id="rfc.iref.d.158"></span> <span id="rfc.iref.c.176"></span>
 (DAV:update-activity-reference): If the request-URL identifies an 
activity, any reference to that activity in a DAV:activity-set, 
DAV:subactivity-set, or DAV:current-activity-set <em class="bcp14">MUST</em> be updated to refer to the new location of that activity.</li><li><span id="rfc.iref.d.159"></span> <span id="rfc.iref.c.177"></span>
 (DAV:update-workspace-reference): If the request-URL identifies a 
workspace, any reference to that workspace in a 
DAV:current-workspace-set property <em class="bcp14">MUST</em> be updated to refer to the new location of that workspace.</li></ul></div></section><section id="n-additional-checkout-semantics_3"><h3 id="rfc.section.13.10"><a href="#rfc.section.13.10">13.10</a>&nbsp;<a href="#n-additional-checkout-semantics_3">Additional CHECKOUT Semantics</a></h3><div id="rfc.section.13.10.p.1"><p>A CHECKOUT request <em class="bcp14">MAY</em> specify the DAV:activity-set for the checked-out resource.<a class="self" href="#rfc.section.13.10.p.1">¶</a></p></div><div id="rfc.section.13.10.p.2"><p><span id="rfc.iref.c.178"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.13.10.p.2">¶</a></p><ul class="empty"><li><span id="rfc.figure.u.137"><pre class="inline">&lt;!ELEMENT checkout ANY&gt; ANY value: A sequence of elements with at
most one DAV:activity-set and at most one DAV:unreserved.

&lt;!ELEMENT activity-set (href+ | new)&gt;
&lt;!ELEMENT new EMPTY&gt;
&lt;!ELEMENT unreserved EMPTY&gt;
</pre></span></li></ul></div><div id="rfc.section.13.10.p.3"><p><span id="rfc.iref.c.179"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.13.10.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.160"></span> <span id="rfc.iref.c.180"></span>
 (DAV:one-checkout-per-activity-per-history): If there is a request 
activity set, unless DAV:unreserved is specified, another checkout from a
 version of that version history <em class="bcp14">MUST NOT</em> select an activity in that activity set.</li><li><span id="rfc.iref.d.161"></span> <span id="rfc.iref.c.181"></span> (DAV:linear-activity): If there is a request activity set, unless DAV:unreserved is specified, the selected version <em class="bcp14">MUST</em> be a descendant of all other versions of that version history that select that activity.</li></ul></div><div id="rfc.section.13.10.p.4"><p><span id="rfc.iref.c.182"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.13.10.p.4">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.162"></span> <span id="rfc.iref.c.183"></span> (DAV:initialize-activity-set): The DAV:activity-set of the checked-out resource is set as follows: <ul><li>If DAV:new is specified as the DAV:activity-set in the request body, then a new activity created by the server is used.</li><li>Otherwise, if activities are specified in the request body, then those activities are used.</li><li>Otherwise,
 if the version-controlled resource is a member of a workspace and the 
DAV:current-activity-set of the workspace is set, then those activities 
are used.</li><li>Otherwise, the DAV:activity-set of the DAV:checked-out version is used.</li></ul> </li><li><span id="rfc.iref.d.163"></span> <span id="rfc.iref.c.184"></span>
 (DAV:initialize-unreserved): If DAV:unreserved was specified in the 
request body, then the DAV:unreserved property of the checked-out 
resource <em class="bcp14">MUST</em> be "true".</li></ul></div><section id="n-example---checkout-with-an-activity"><h4 id="rfc.section.13.10.1"><a href="#rfc.section.13.10.1">13.10.1</a>&nbsp;<a href="#n-example---checkout-with-an-activity">Example - CHECKOUT with an activity</a></h4><div id="rfc.figure.u.138"><p>&gt;&gt;REQUEST</p><pre class="text2">CHECKOUT /ws/public/foo.html HTTP/1.1
Host: www.webdav.org
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx

&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;D:checkout xmlns:D="DAV:"&gt;
  &lt;D:activity-set&gt;
    &lt;D:href&gt;http://repo.webdav.org/act/fix-bug-23&lt;/D:href&gt;
  &lt;/D:activity-set&gt;
&lt;/D:checkout&gt;
</pre></div><div id="rfc.figure.u.139"><p>&gt;&gt;RESPONSE</p><pre class="text">HTTP/1.1 200 OK
Cache-Control: no-cache
</pre></div><div id="rfc.section.13.10.1.p.1"><p>In this example, the CHECKOUT is being performed in the http://repo.webdav.org/act/fix-bug-23 activity.<a class="self" href="#rfc.section.13.10.1.p.1">¶</a></p></div></section></section><section id="n-additional-checkin-semantics_4"><h3 id="rfc.section.13.11"><a href="#rfc.section.13.11">13.11</a>&nbsp;<a href="#n-additional-checkin-semantics_4">Additional CHECKIN Semantics</a></h3><div id="rfc.section.13.11.p.1"><p><span id="rfc.iref.c.185"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.13.11.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.164"></span> <span id="rfc.iref.c.186"></span>
 (DAV:linear-activity): Any version which is in the version history of 
the checked-out resource and whose DAV:activity-set identifies an 
activity from the DAV:activity-set of the checked-out resource <em class="bcp14">MUST</em> be an ancestor of the checked-out resource.</li><li><span id="rfc.iref.d.165"></span> <span id="rfc.iref.c.187"></span> (DAV:atomic-activity-checkin): If the request-URL identifies an activity, the server <em class="bcp14">MAY</em>
 fail the request if any of the checked-out resources in the 
DAV:activity-checkout-set of either that activity or any subactivity of 
that activity cannot be checked in.</li></ul></div><div id="rfc.section.13.11.p.2"><p><span id="rfc.iref.c.188"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.13.11.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.166"></span> <span id="rfc.iref.c.189"></span> (DAV:initialize-activity-set): The DAV:activity-set of the new version <em class="bcp14">MUST</em> have been initialized to be the same as the DAV:activity-set of the checked-out resource.</li><li><span id="rfc.iref.d.167"></span> <span id="rfc.iref.c.190"></span> (DAV:activity-checkin): If the request-URL identified an activity, the server <em class="bcp14">MUST</em>
 have successfully applied the CHECKIN request to each checked-out 
resource in the DAV:activity-checkout-set of both that activity and any 
subactivity of that activity.</li></ul></div></section><section id="n-additional-merge-semantics_2"><h3 id="rfc.section.13.12"><a href="#rfc.section.13.12">13.12</a>&nbsp;<a href="#n-additional-merge-semantics_2">Additional MERGE Semantics</a></h3><div id="rfc.section.13.12.p.1"><p>If
 the DAV:source element of the request body identifies an activity, then
 for each version history containing a version selected by that 
activity, the latest version selected by that activity is a merge 
source. Note that the versions selected by an activity are the versions 
in its DAV:activity-version-set unioned with the versions selected by 
the activities in its DAV:subactivity-set.<a class="self" href="#rfc.section.13.12.p.1">¶</a></p></div><div id="rfc.section.13.12.p.2"><p><span id="rfc.iref.m.21"></span> <b>Additional Marshalling:</b> <a class="self" href="#rfc.section.13.12.p.2">¶</a></p><ul class="empty"><li><span id="rfc.figure.u.140"><pre class="inline">&lt;!ELEMENT checkin-activity EMPTY&gt;
</pre></span></li></ul></div><div id="rfc.section.13.12.p.3"><p><span id="rfc.iref.m.22"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.13.12.p.3">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.168"></span> <span id="rfc.iref.c.191"></span>
 (DAV:checkin-activity): If DAV:checkin-activity is specified in the 
request body, and if the DAV:source element in the request body 
identifies an activity, a CHECKIN request <em class="bcp14">MUST</em> have been successfully applied to that activity before the merge sources were determined.</li></ul></div></section></section><hr class="noprint"><section id="version-controlled-collection.feature"><h2 id="rfc.section.14" class="np"><a href="#rfc.section.14">14.</a>&nbsp;<a href="#version-controlled-collection.feature">Version-Controlled-Collection Feature</a></h2><div id="rfc.section.14.p.1"><p>As
 with any versionable resource, when a collection is put under version 
control, a version history resource is created to contain versions for 
that version-controlled collection. In order to preserve standard 
versioning semantics (a version of a collection should not be 
modifiable), a collection version only records information about the 
version-controlled bindings of that collection.<a class="self" href="#rfc.section.14.p.1">¶</a></p></div><div id="rfc.section.14.p.2"><p>In
 order to cleanly separate a modification to the namespace from a 
modification to content or dead properties, a version of a collection 
has no members, but instead records in its 
DAV:version-controlled-binding-set property the binding name and version
 history resource of each version-controlled internal member of that 
collection. If, instead, a collection version contained bindings to 
other versions, creating a new version of a resource would require 
creating a new version of all the collection versions that contain that 
resource, which would cause activities to become entangled. For example,
 suppose a "feature-12" activity created a new version of /x/y/a.html. 
If a collection version contained bindings to versions of its members, a
 new version of /x/y would have to be created to contain the new version
 of /x/y/a.html, and a new version of /x would have to be created to 
contain the new version of /x/y. Now suppose a "bugfix-47" activity 
created a new version of /x/z/b.html. Again, a new version of /x/z and a
 new version of /x would have to be created to contain the new version 
of /x/y/b.html. But now it is impossible to merge just "bugfix-47" into 
another workspace without "feature-12", because the version of /x that 
contains the desired version of /x/z/b.html also contains version of 
/x/y/a.html created for "feature-12". If, instead, a collection version 
just records the binding name and version history resource of each 
version-controlled internal member, changing the version selected by a 
member of that collection would not require a new version of the 
collection. The new version is still in the same version history so no 
new collection version is required, and "feature-12" and "bugfix-47" 
would not become entangled.<a class="self" href="#rfc.section.14.p.2">¶</a></p></div><div id="rfc.section.14.p.3"><p>In
 the following example, there are three version histories, named VH14, 
VH19, and VH24, where VH14 contains versions of a collection. The 
version-controlled collection /x has version V2 of version history VH14 
as its DAV:checked-in version. Since V2 has recorded two version 
controlled bindings, one with binding name "a" to version history VH19, 
and the other with binding name "b" to version history VH24, /x <em class="bcp14">MUST</em>
 have two version-controlled bindings, one named "a" to a 
version-controlled resource for history VH19, and the other named "b" to
 a version-controlled resource for history VH24. The version-controlled 
resource /x/a currently has V4 of VH19 as its DAV:checked-in version, 
while /x/b has V8 of VH24 as its DAV:checked-in version.<a class="self" href="#rfc.section.14.p.3">¶</a></p></div><div id="rfc.figure.u.141"><pre class="drawing">                                                          VH19
                                                       ┌─────────┐
                                                       │ ┌───┐   │ 
                                                       │ │   │V4 │
                                                       │ └───┘   │
                                                       │   |     │
                                                       │   |     │
                                                       │ ┌───┐   │
                                                       │ │   │V5 │
                                            VH14       │ └───┘   │
                                        ┌─────────┐    │   |     │
                                        │ ┌───┐   │    │   |     │
               a  ┌───┐                 │ │   │V1 │    │ ┌───┐   │
             ----&gt;│   │checked-in=V4    │ └───┘   │ a  │ │   │V6 │
            /     └───┘                 │   |   --│---&gt;│ └───┘   │
           /                            │   |  /  │    └─────────┘
      ┌───┐                             │ ┌───┐   │
   /x │   │checked-in=V2                │ │   │V2 │
      └───┘                             │ └───┘   │       VH24
           \                            │   |  \  │ b  ┌─────────┐
            \  b  ┌───┐                 │   |   --│---&gt;│ ┌───┐   │
             ----&gt;│   │checked-in=V8    │ ┌───┐   │    │ │   │V7 │
                  └───┘                 │ │   │V3 │    │ └───┘   │
                                        │ └───┘   │    │   |     │
                                        └─────────┘    │   |     │
                                                       │ ┌───┐   │
                                                       │ │   │V8 │
                                                       │ └───┘   │
                                                       │   |     │
                                                       │   |     │
                                                       │ ┌───┐   │
                                                       │ │   │V9 │
                                                       │ └───┘   │
                                                       └─────────┘
</pre></div><div id="rfc.section.14.p.4"><p>For any request (e.g., 
DELETE, MOVE, COPY) that modifies a version-controlled binding of a 
checked-in version-controlled collection, the request <em class="bcp14">MUST</em>
 fail unless the version-controlled collection has a DAV:auto-version 
property that will automatically check out the version-controlled 
collection when it is modified.<a class="self" href="#rfc.section.14.p.4">¶</a></p></div><div id="rfc.section.14.p.5"><p>Although a collection version only records the version-controlled bindings of a collection, a version-controlled collection <em class="bcp14">MAY</em>
 contain both version-controlled and non-version-controlled bindings. 
Non-version-controlled bindings are not under version control, and 
therefore can be added or deleted without checking out the 
version-controlled collection.<a class="self" href="#rfc.section.14.p.5">¶</a></p></div><div id="rfc.section.14.p.6"><p>Note
 that a collection version captures only a defined subset of the state 
of a collection. In particular, a version of a collection captures its 
dead properties and its bindings to version-controlled resources, but 
not its live properties or bindings to non-version-controlled resources.<a class="self" href="#rfc.section.14.p.6">¶</a></p></div><div id="rfc.section.14.p.7"><p>When
 a server supports the working-resource feature, a client can check out a
 collection version to create a working collection. Unlike a 
version-controlled collection, which contains bindings to 
version-controlled resources and non-version-controlled resources, a 
working collection contains bindings to version history resources and 
non-version-controlled resources. In particular, a working collection is
 initialized to contain bindings to the version history resources 
specified by the DAV:version-controlled-binding-set of the checked out 
collection version. The members of a working collection can then be 
deleted or moved to another working collection. Non-version-controlled 
resources can be added to a working collection with methods such as PUT,
 COPY, and MKCOL. When a working collection is checked in, a 
VERSION-CONTROL request is automatically applied to every 
non-version-controlled member of the working collection, and each 
non-version-controlled member is replaced by its newly created version 
history. The DAV:version-controlled-binding-set of the new version 
resulting from checking in a working collection contains the binding 
name and version history URL for each member of the working collection.<a class="self" href="#rfc.section.14.p.7">¶</a></p></div><section id="n-version-controlled-collection-properties"><h3 id="rfc.section.14.1"><a href="#rfc.section.14.1">14.1</a>&nbsp;<a href="#n-version-controlled-collection-properties">Version-Controlled Collection Properties</a></h3><div id="rfc.section.14.1.p.1"><p>A
 version-controlled collection has all the properties of a collection 
and of a version-controlled resource. In addition, the 
version-controlled-collection feature introduces the following <em class="bcp14">REQUIRED</em> property for a version-controlled collection.<a class="self" href="#rfc.section.14.1.p.1">¶</a></p></div><section id="PROPERTY_eclipsed-set"><h4 id="rfc.section.14.1.1"><a href="#rfc.section.14.1.1">14.1.1</a>&nbsp;<a href="#PROPERTY_eclipsed-set">DAV:eclipsed-set (computed)</a></h4><div id="rfc.section.14.1.1.p.1"><p>This
 property identifies the non-version-controlled internal members of the 
collection that currently are eclipsing a version-controlled internal 
member of the collection. <a class="self" href="#rfc.section.14.1.1.p.1">¶</a></p><span id="rfc.figure.u.142"><pre class="inline">!ELEMENT eclipsed-set (binding-name*)&gt;
&lt;!ELEMENT binding-name (#PCDATA)&gt;
PCDATA value: URL segment
</pre></span></div><div id="rfc.section.14.1.1.p.2"><p>An UPDATE or 
MERGE request can give a version-controlled collection a 
version-controlled internal member that has the same name as an existing
 non-version-controlled internal member. In this case, the 
non-version-controlled internal member takes precedence and is said to 
"eclipse" the new versioned-controlled internal member. If the 
non-version-controlled internal member is removed (e.g., by a DELETE or 
MOVE), the version-controlled internal member is exposed.<a class="self" href="#rfc.section.14.1.1.p.2">¶</a></p></div></section></section><section id="n-collection-version-properties"><h3 id="rfc.section.14.2"><a href="#rfc.section.14.2">14.2</a>&nbsp;<a href="#n-collection-version-properties">Collection Version Properties</a></h3><div id="rfc.section.14.2.p.1"><p>A
 collection version has all the properties of a version. In addition, 
the version-controlled-collection feature introduces the following <em class="bcp14">REQUIRED</em> property for a collection version.<a class="self" href="#rfc.section.14.2.p.1">¶</a></p></div><section id="PROPERTY_version-controlled-binding-set"><h4 id="rfc.section.14.2.1"><a href="#rfc.section.14.2.1">14.2.1</a>&nbsp;<a href="#PROPERTY_version-controlled-binding-set">DAV:version-controlled-binding-set (protected)</a></h4><div id="rfc.section.14.2.1.p.1"><p>This property captures the name and version-history of each version-controlled internal member of a collection. <a class="self" href="#rfc.section.14.2.1.p.1">¶</a></p><span id="rfc.figure.u.143"><pre class="inline">&lt;!ELEMENT version-controlled-binding-set
 (version-controlled-binding*)&gt;
&lt;!ELEMENT version-controlled-binding
 (binding-name, version-history)&gt;
&lt;!ELEMENT binding-name (#PCDATA)&gt;
PCDATA value: URL segment
&lt;!ELEMENT version-history (href)&gt;
</pre></span></div></section></section><section id="n-additional-options-semantics_10"><h3 id="rfc.section.14.3"><a href="#rfc.section.14.3">14.3</a>&nbsp;<a href="#n-additional-options-semantics_10">Additional OPTIONS Semantics</a></h3><div id="rfc.section.14.3.p.1"><p>If the server supports the version-controlled-collection feature, it <em class="bcp14">MUST</em>
 include "version-controlled-collection" as a field in the DAV response 
header from an OPTIONS request on any resource that supports any 
versioning properties, reports, or methods.<a class="self" href="#rfc.section.14.3.p.1">¶</a></p></div></section><section id="n-additional-delete-semantics_5"><h3 id="rfc.section.14.4"><a href="#rfc.section.14.4">14.4</a>&nbsp;<a href="#n-additional-delete-semantics_5">Additional DELETE Semantics</a></h3><div id="rfc.section.14.4.p.1"><p><span id="rfc.iref.d.169"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.14.4.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.170"></span> <span id="rfc.iref.c.192"></span> (DAV:cannot-modify-checked-in-parent): If the request-URL identifies a version-controlled resource, the DELETE <em class="bcp14">MUST</em>
 fail when the collection containing the version-controlled resource is a
 checked-in version-controlled collection, unless DAV:auto-version 
semantics will automatically check out the version-controlled 
collection.</li></ul></div></section><section id="n-additional-mkcol-semantics_2"><h3 id="rfc.section.14.5"><a href="#rfc.section.14.5">14.5</a>&nbsp;<a href="#n-additional-mkcol-semantics_2">Additional MKCOL Semantics</a></h3><div id="rfc.section.14.5.p.1"><p><span id="rfc.iref.m.23"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.14.5.p.1">¶</a></p><ul class="empty"><li>If
 the request creates a new resource that is automatically placed under 
version control, all preconditions for VERSION-CONTROL apply to the 
request.</li></ul></div><div id="rfc.section.14.5.p.2"><p><span id="rfc.iref.m.24"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.14.5.p.2">¶</a></p><ul class="empty"><li>If the new collection is automatically put under version control, all postconditions for VERSION-CONTROL apply to the request.</li></ul></div></section><section id="n-additional-copy-semantics_6"><h3 id="rfc.section.14.6"><a href="#rfc.section.14.6">14.6</a>&nbsp;<a href="#n-additional-copy-semantics_6">Additional COPY Semantics</a></h3><div id="rfc.section.14.6.p.1"><p><span id="rfc.iref.c.193"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.14.6.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.171"></span> <span id="rfc.iref.c.194"></span> (DAV:cannot-copy-collection-version): If the source of the request is a collection version, the request <em class="bcp14">MUST</em> fail.</li></ul></div></section><section id="n-additional-move-semantics_6"><h3 id="rfc.section.14.7"><a href="#rfc.section.14.7">14.7</a>&nbsp;<a href="#n-additional-move-semantics_6">Additional MOVE Semantics</a></h3><div id="rfc.section.14.7.p.1"><p><span id="rfc.iref.m.25"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.14.7.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.172"></span> <span id="rfc.iref.c.195"></span> (DAV:cannot-modify-checked-in-parent): If the source of the request is a version-controlled resource, the request <em class="bcp14">MUST</em>
 fail when the collection containing the source is a checked-in 
version-controlled collection, unless DAV:auto-version semantics will 
automatically check out that version-controlled collection.</li><li><span id="rfc.iref.d.173"></span> <span id="rfc.iref.c.196"></span> (DAV:cannot-modify-destination-checked-in-parent): If the source of the request is a version-controlled resource, the request <em class="bcp14">MUST</em>
 fail when the collection containing the destination is a checked-in 
version-controlled collection, unless DAV:auto-version semantics will 
automatically check out that version-controlled collection.</li></ul></div></section><section id="n-additional-version-control-semantics_3"><h3 id="rfc.section.14.8"><a href="#rfc.section.14.8">14.8</a>&nbsp;<a href="#n-additional-version-control-semantics_3">Additional VERSION-CONTROL Semantics</a></h3><div id="rfc.section.14.8.p.1"><p><span id="rfc.iref.v.14"></span> <b>Additional Preconditions:</b> <a class="self" href="#rfc.section.14.8.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.174"></span> <span id="rfc.iref.c.197"></span>
 (DAV:cannot-modify-checked-in-parent): If the parent of the request-URL
 is a checked-in version-controlled collection, the request <em class="bcp14">MUST</em> fail unless DAV:auto-version semantics will automatically check out that version-controlled collection.</li></ul></div><div id="rfc.section.14.8.p.2"><p><span id="rfc.iref.v.15"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.14.8.p.2">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.175"></span> <span id="rfc.iref.c.198"></span>
 (DAV:new-version-controlled-collection): If the request body identified
 a collection version, the collection at the request-URL <em class="bcp14">MUST</em>
 contain a version-controlled internal member for each 
DAV:version-controlled-binding specified in the 
DAV:version-controlled-binding-set of the collection version, where the 
name and DAV:version-history of the internal member <em class="bcp14">MUST</em>
 be the DAV:binding-name and the DAV:version-history specified by the 
DAV:version-controlled-binding. If the internal member is a member of a 
workspace, and there is another member of the workspace for the same 
version history, those two members <em class="bcp14">MUST</em> identify 
the same version-controlled resource; otherwise, a VERSION-CONTROL 
request with a server selected version of the version history <em class="bcp14">MUST</em> have been applied to the URL for that internal member.</li></ul></div></section><section id="n-additional-checkout-semantics_4"><h3 id="rfc.section.14.9"><a href="#rfc.section.14.9">14.9</a>&nbsp;<a href="#n-additional-checkout-semantics_4">Additional CHECKOUT Semantics</a></h3><div id="rfc.section.14.9.p.1"><p><span id="rfc.iref.c.199"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.14.9.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.176"></span> <span id="rfc.iref.c.200"></span> (DAV:initialize-version-history-bindings): If the request has been applied to a collection version, the new working collection <em class="bcp14">MUST</em>
 be initialized to contain a binding to each of the history resources 
identified in the DAV:version-controlled-binding-set of that collection 
version.</li></ul></div></section><section id="n-additional-checkin-semantics_5"><h3 id="rfc.section.14.10"><a href="#rfc.section.14.10">14.10</a>&nbsp;<a href="#n-additional-checkin-semantics_5">Additional CHECKIN Semantics</a></h3><div id="rfc.section.14.10.p.1"><p><span id="rfc.iref.c.201"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.14.10.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.177"></span> <span id="rfc.iref.c.202"></span>
 (DAV:initialize-version-controlled-bindings): If the request-URL 
identified a version-controlled collection, then the 
DAV:version-controlled-binding-set of the new collection version <em class="bcp14">MUST</em>
 contain a DAV:version-controlled-binding that identifies the binding 
name and version history for each version-controlled binding of the 
version-controlled collection.</li><li><span id="rfc.iref.d.178"></span> <span id="rfc.iref.c.203"></span>
 (DAV:version-control-working-collection-members): If the request-URL 
identified a working collection, a VERSION-CONTROL request <em class="bcp14">MUST</em>
 have been automatically applied to every non-version-controlled member 
of the working collection, and each non-version-controlled member <em class="bcp14">MUST</em>
 have been replaced by its newly created version history. If a working 
collection member was a non-version-controlled collection, every member 
of the non-version-controlled collection <em class="bcp14">MUST</em> 
have been placed under version control before the non-version-controlled
 collection was placed under version control. The 
DAV:version-controlled-binding-set of the new collection version <em class="bcp14">MUST</em>
 contain a DAV:version-controlled-binding that identifies the binding 
name and the version history URL for each member of the working 
collection.</li></ul></div></section><section id="n-additional-update-and-merge-semantics"><h3 id="rfc.section.14.11"><a href="#rfc.section.14.11">14.11</a>&nbsp;<a href="#n-additional-update-and-merge-semantics">Additional UPDATE and MERGE Semantics</a></h3><div id="rfc.section.14.11.p.1"><p><span id="rfc.iref.u.13"></span><span id="rfc.iref.m.26"></span> <b>Additional Postconditions:</b> <a class="self" href="#rfc.section.14.11.p.1">¶</a></p><ul class="empty"><li><span id="rfc.iref.d.179"></span> <span id="rfc.iref.c.204"></span>
 (DAV:update-version-controlled-collection-members): If the request 
modified the DAV:checked-in version of a version-controlled collection, 
then the version-controlled members of that version-controlled 
collection <em class="bcp14">MUST</em> have been updated. In particular: <ul><li>A version-controlled internal member <em class="bcp14">MUST</em>
 have been deleted if its version history is not identified by the 
DAV:version-controlled-binding-set of the new DAV:checked-in version.</li><li>A version-controlled internal member for a given version history <em class="bcp14">MUST</em>
 have been renamed if its binding name differs from the DAV:binding-name
 for that version history in the DAV:version-controlled-binding-set of 
the new DAV:checked-in version.</li><li>A new version-controlled internal member <em class="bcp14">MUST</em>
 have been created when a version history is identified by the 
DAV:version-controlled-binding-set of the DAV:checked-in version, but 
there was no member of the version-controlled collection for that 
version history. If a new version-controlled member is in a workspace 
that already has a version-controlled resource for that version history,
 then the new version-controlled member <em class="bcp14">MUST</em> be 
just a binding (i.e., another name for) that existing version-controlled
 resource. Otherwise, the content and dead properties of the new 
version-controlled member <em class="bcp14">MUST</em> have been 
initialized to be those of the version specified for that version 
history by the request. If no version is specified for that version 
history by the request, the version selected is server defined.</li></ul> </li></ul></div></section></section><hr class="noprint"><section id="n-internationalization-considerations"><h2 id="rfc.section.15" class="np"><a href="#rfc.section.15">15.</a>&nbsp;<a href="#n-internationalization-considerations">Internationalization Considerations</a></h2><div id="rfc.section.15.p.1"><p>This specification has been designed to be compliant with the IETF Policy on Character Sets and Languages <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
 Specifically, where human-readable strings exist in the protocol, 
either their charset is explicitly stated, or XML mechanisms are used to
 specify the charset used. Additionally, these human-readable strings 
all have the ability to express the natural language of the string.<a class="self" href="#rfc.section.15.p.1">¶</a></p></div><div id="rfc.section.15.p.2"><p>Most
 of the human-readable strings in this protocol appear in properties, 
such as DAV:creator-displayname. As defined by RFC 2518, properties have
 their values marshaled as XML. XML has explicit provisions for 
character set tagging and encoding, and requires that XML processors 
read XML elements encoded, at minimum, using the UTF-8 <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a>
 encoding of the ISO 10646 multilingual plane. The charset parameter of 
the Content-Type header, together with the XML "encoding" attribute, 
provide charset identification information for MIME and XML processors. 
Proper use of the charset header with XML is described in <cite title="XML Media Types" id="rfc.xref.RFC3023.1">RFC 3023</cite>.
 XML also provides a language tagging capability for specifying the 
language of the contents of a particular XML element. XML uses either 
IANA registered language tags (see <cite title="Tags for the Identification of Languages" id="rfc.xref.RFC3066.1">RFC 3066</cite>) or <cite title="ISO 639:1988. Code for the representation of names of languages." id="rfc.xref.ISO639.1">ISO 639</cite> language tags in the "xml:lang" attribute of an XML element to identify the language of its content and attributes.<a class="self" href="#rfc.section.15.p.2">¶</a></p></div><div id="rfc.section.15.p.3"><p>DeltaV applications, since they build upon WebDAV, are subject to the internationalization requirements specified in RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-16" id="rfc.xref.RFC2518.12">Section 16</a>.
 In brief, these requirements mandate the use of XML character set 
tagging, character set encoding, and language tagging capabilities. 
Additionally, they strongly recommend reading RFC 3023 for instruction 
on the use of MIME media types for XML transport and the use of the 
charset header.<a class="self" href="#rfc.section.15.p.3">¶</a></p></div><div id="rfc.section.15.p.4"><p>Within
 this specification, a label is a human-readable string that is 
marshaled in the Label header and as XML in request entity bodies. When 
used in the Label header, the value of the label is URL-escaped and 
encoded using UTF-8.<a class="self" href="#rfc.section.15.p.4">¶</a></p></div></section><hr class="noprint"><section id="n-security-considerations"><h2 id="rfc.section.16" class="np"><a href="#rfc.section.16">16.</a>&nbsp;<a href="#n-security-considerations">Security Considerations</a></h2><div id="rfc.section.16.p.1"><p>All of the security considerations of WebDAV discussed in RFC 2518, <a href="https://tools.ietf.org/html/rfc2518#section-17" id="rfc.xref.RFC2518.13">Section 17</a>
 also apply to WebDAV versioning. Some aspects of the versioning 
protocol help address security risks introduced by WebDAV, but other 
aspects can increase these security risks. These issues are detailed 
below.<a class="self" href="#rfc.section.16.p.1">¶</a></p></div><section id="n-auditing-and-traceability"><h3 id="rfc.section.16.1"><a href="#rfc.section.16.1">16.1</a>&nbsp;<a href="#n-auditing-and-traceability">Auditing and Traceability</a></h3><div id="rfc.section.16.1.p.1"><p>WebDAV
 increases the ease with which a remote client can modify resources on a
 web site, but this also increases the risk of important information 
being overwritten and lost, either through user error or user 
maliciousness. The use of WebDAV versioning can help address this 
problem by guaranteeing that previous information is saved in the form 
of immutable versions, and therefore is easily available for retrieval 
or restoration. In addition, the version history provides a log of when 
changes were made, and by whom. When requests are appropriately 
authenticated, the history mechanism provides a clear audit trail for 
changes to web resources. This can often significantly improve the 
ability to identify the source of the security problem, and thereby help
 guard against it in the future.<a class="self" href="#rfc.section.16.1.p.1">¶</a></p></div></section><section id="n-increased-need-for-access-control"><h3 id="rfc.section.16.2"><a href="#rfc.section.16.2">16.2</a>&nbsp;<a href="#n-increased-need-for-access-control">Increased Need for Access Control</a></h3><div id="rfc.section.16.2.p.1"><p>WebDAV
 versioning provides a variety of links between related pieces of 
information. This can increase the risk that authentication or 
authorization errors allow a client to locate sensitive information. For
 example, if version history is not appropriately protected by access 
control, a client can use the version history of a public resource to 
identify later versions of that resource that the user intended to keep 
private. This increases the need for reliable authentication and 
accurate authorization.<a class="self" href="#rfc.section.16.2.p.1">¶</a></p></div><div id="rfc.section.16.2.p.2"><p>A
 WebDAV versioning client should be designed to handle a mixture of 200 
(OK) and 403 (Forbidden) responses on attempts to access the properties 
and reports that are supported by a resource. For example, a particular 
user may be authorized to access the content and dead properties of a 
version-controlled resource, but not be authorized to access the 
DAV:checked-in, DAV:checked-out, or DAV:version-history properties of 
that resource.<a class="self" href="#rfc.section.16.2.p.2">¶</a></p></div></section><section id="n-security-through-obscurity"><h3 id="rfc.section.16.3"><a href="#rfc.section.16.3">16.3</a>&nbsp;<a href="#n-security-through-obscurity">Security Through Obscurity</a></h3><div id="rfc.section.16.3.p.1"><p>While
 it is acknowledged that "obscurity" is not an effective means of 
security, it is often a good technique to keep honest people honest. 
Within this protocol, version URLs, version history URLs, and working 
resource URLs are generated by the server and can be properly obfuscated
 so as not to draw attention to them. For example, a version of 
"http://foobar.com/reviews/salaries.html" might be assigned a URL such 
as "http://foobar.com/repo/4934943".<a class="self" href="#rfc.section.16.3.p.1">¶</a></p></div></section><section id="n-denial-of-service"><h3 id="rfc.section.16.4"><a href="#rfc.section.16.4">16.4</a>&nbsp;<a href="#n-denial-of-service">Denial of Service</a></h3><div id="rfc.section.16.4.p.1"><p>The
 auto-versioning mechanism provided by WebDAV can result in a large 
number of resources being created on the server, since each update to a 
resource could potentially result in the creation of a new version 
resource. This increases the risk of a denial of service attack that 
exhausts the storage capability of a server. This risk is especially 
significant because it can be an unintentional result of something like 
an aggressive auto-save feature provided by an editing client. A server 
can decrease this risk by using delta storage techniques to minimize the
 cost of additional versions, and by limiting auto-versioning to a 
locking client, and thereby decreasing the number of inadvertent version
 creations.<a class="self" href="#rfc.section.16.4.p.1">¶</a></p></div></section></section><hr class="noprint"><section id="n-iana-considerations"><h2 id="rfc.section.17" class="np"><a href="#rfc.section.17">17.</a>&nbsp;<a href="#n-iana-considerations">IANA Considerations</a></h2><div id="rfc.section.17.p.1"><p>This
 document uses the namespace defined by RFC 2518 for XML elements. All 
other IANA considerations from RFC 2518 are also applicable to WebDAV 
Versioning.<a class="self" href="#rfc.section.17.p.1">¶</a></p></div></section><hr class="noprint"><section id="n-intellectual-property"><h2 id="rfc.section.18" class="np"><a href="#rfc.section.18">18.</a>&nbsp;<a href="#n-intellectual-property">Intellectual Property</a></h2><div id="rfc.section.18.p.1"><p>The following notice is copied from <cite title="The Internet Standards Process -- Revision 3" id="rfc.xref.RFC2026.1">RFC 2026</cite>, <a href="https://tools.ietf.org/html/rfc2026#section-10.4" id="rfc.xref.RFC2026.2">Section 10.4</a>, and describes the position of the IETF concerning intellectual property claims made against this document.<a class="self" href="#rfc.section.18.p.1">¶</a></p></div><div id="rfc.section.18.p.2"><p>The
 IETF takes no position regarding the validity or scope of any 
intellectual property or other rights that might be claimed to pertain 
to the implementation or use other technology described in this document
 or the extent to which any license under such rights might or might not
 be available; neither does it represent that it has made any effort to 
identify any such rights. Information on the procedures of the IETF with
 respect to rights in standards-track and standards-related 
documentation can be found in BCP-11. Copies of claims of rights made 
available for publication and any assurances of licenses to be made 
available, or the result of an attempt made to obtain a general license 
or permission for the use of such proprietary rights by implementers or 
users of this specification can be obtained from the IETF Secretariat.<a class="self" href="#rfc.section.18.p.2">¶</a></p></div><div id="rfc.section.18.p.3"><p>The
 IETF invites any interested party to bring to its attention any 
copyrights, patents or patent applications, or other proprietary rights 
that may cover technology that may be required to practice this 
standard. Please address the information to the IETF Executive Director.<a class="self" href="#rfc.section.18.p.3">¶</a></p></div></section><hr class="noprint"><section id="n-acknowledgements"><h2 id="rfc.section.19" class="np"><a href="#rfc.section.19">19.</a>&nbsp;<a href="#n-acknowledgements">Acknowledgements</a></h2><div id="rfc.section.19.p.1"><p>This
 protocol is the collaborative product of the authors and the rest of 
the DeltaV design team: Boris Bokowski, Bruce Cragun (Novell), Jim 
Doubek (Macromedia), David Durand (INSO), Lisa Dusseault (Xythos), Chuck
 Fay (FileNet), Yaron Goland, Mark Hale (Interwoven), Henry Harbury 
(Merant), James Hunt, Jeff McAffer (OTI), Peter Raymond (Merant), 
Juergen Reuter, Edgar Schwarz (Marconi), Eric Sedlar (Oracle), Bradley 
Sergeant, Greg Stein, and John Vasta (Rational). We would like to 
acknowledge the foundation laid for us by the authors of the WebDAV and 
HTTP protocols upon which this protocol is layered, and the invaluable 
feedback from the WebDAV and DeltaV working groups.<a class="self" href="#rfc.section.19.p.1">¶</a></p></div></section><section id="rfc.references" class="np"><h2 id="rfc.section.20"><a href="#rfc.section.20">20.</a> References</h2><dl class="reference"><dt id="ISO639">[ISO639]</dt><dd><a href="http://www.iso.ch/">International Organization for Standardization</a>, “ISO 639:1988. Code for the representation of names of languages.”, 1988.</dd><dt id="RFC2026">[RFC2026]</dt><dd><a href="mailto:sob@harvard.edu">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2026">The Internet Standards Process -- Revision 3</a>”, BCP&nbsp;9, RFC&nbsp;2026, October&nbsp;1996.</dd><dt id="RFC2119">[RFC2119]</dt><dd><a href="mailto:sob@harvard.edu">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.</dd><dt id="RFC2277">[RFC2277]</dt><dd><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.</a>, “<a href="https://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.</dd><dt id="RFC2279">[RFC2279]</dt><dd><a href="mailto:fyergeau@alis.com">Yergeau, F.</a>, “<a href="https://tools.ietf.org/html/rfc2279">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;2279, January&nbsp;1998.</dd><dt id="RFC2396">[RFC2396]</dt><dd><a href="mailto:timbl@w3.org">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu">Fielding, R.</a>, and <a href="mailto:masinter@parc.xerox.com">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC&nbsp;2396, August&nbsp;1998.</dd><dt id="RFC2518">[RFC2518]</dt><dd><a href="mailto:yarong@microsoft.com">Goland, Y.</a>, <a href="mailto:ejw@ics.uci.edu">Whitehead, E.</a>, <a href="mailto:asad@netscape.com">Faizi, A.</a>, <a href="mailto:srcarter@novell.com">Carter, S.</a>, and <a href="mailto:dcjensen@novell.com">D. Jensen</a>, “<a href="https://tools.ietf.org/html/rfc2518">HTTP Extensions for Distributed Authoring -- WEBDAV</a>”, RFC&nbsp;2518, February&nbsp;1999.</dd><dt id="RFC2616">[RFC2616]</dt><dd><a href="mailto:fielding@ics.uci.edu">Fielding, R.</a>, <a href="mailto:jg@w3.org">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com">Mogul, J.</a>, <a href="mailto:frystyk@w3.org">Nielsen, H.</a>, <a href="mailto:masinter@parc.xerox.com">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a>, and <a href="mailto:timbl@w3.org">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.</dd><dt id="RFC3023">[RFC3023]</dt><dd><a href="mailto:mmurata@trl.ibm.co.jp">Makoto, M.</a>, <a href="mailto:simonstl@simonstl.com">St.Laurent, S.</a>, and <a href="mailto:dan@dankohn.com">D. Kohn</a>, “<a href="https://tools.ietf.org/html/rfc3023">XML Media Types</a>”, RFC&nbsp;3023, January&nbsp;2001.</dd><dt id="RFC3066">[RFC3066]</dt><dd><a href="mailto:Harald@Alvestrand.no">Alvestrand, H.</a>, “<a href="https://tools.ietf.org/html/rfc3066">Tags for the Identification of Languages</a>”, BCP&nbsp;47, RFC&nbsp;3066, January&nbsp;2001.</dd></dl></section><hr class="noprint"><section id="n-resource-classification"><h2 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#n-resource-classification">Resource Classification</a></h2><div id="rfc.section.A.p.1"><p>This
 document introduces several different kinds of versioning resources, 
such as version-controlled resources, versions, checked- out resources, 
and version history resources. As clients discover resources on a 
server, they may find it useful to classify those resources (for 
example, to make UI decisions on choice of icon and menu options).<a class="self" href="#rfc.section.A.p.1">¶</a></p></div><div id="rfc.section.A.p.2"><p>Clients should classify a resource by examining the values of the DAV:supported-method-set (see <a href="#PROPERTY_supported-method-set" title="DAV:supported-method-set (protected)">Section&nbsp;3.1.3</a>) and DAV:supported-live-property-set (see <a href="#PROPERTY_supported-live-property-set" title="DAV:supported-live-property-set (protected)">Section&nbsp;3.1.4</a>) properties of that resource.<a class="self" href="#rfc.section.A.p.2">¶</a></p></div><div id="rfc.section.A.p.3"><p>The
 following list shows the supported live properties and methods for each
 kind of versioning resource. Where an optional feature introduces a new
 kind of versioning resource, that feature is noted in parentheses 
following the name of that kind of versioning resource. If a live 
property or method is optional for a kind of versioning resource, the 
feature that introduces that live property or method is noted in 
parentheses following the live property or method name.<a class="self" href="#rfc.section.A.p.3">¶</a></p></div><section id="n-deltav-compliant-unmapped-url--a-url-that-identifies-no-resource-"><h3 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#n-deltav-compliant-unmapped-url--a-url-that-identifies-no-resource-">DeltaV-Compliant Unmapped URL (a URL that identifies no resource)</a></h3><div id="rfc.section.A.1.p.1"><p>Supported methods: <a class="self" href="#rfc.section.A.1.p.1">¶</a></p><ul><li>PUT <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a></li><li>MKCOL <a href="#RFC2518" id="rfc.xref.RFC2518.14"><cite title="HTTP Extensions for Distributed Authoring -- WEBDAV">[RFC2518]</cite></a></li><li>MKACTIVITY (activity)</li><li>VERSION-CONTROL (workspace)</li><li>MKWORKSPACE (workspace)</li></ul></div></section><section id="n-deltav-compliant-resource"><h3 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#n-deltav-compliant-resource">DeltaV-Compliant Resource</a></h3><div id="rfc.section.A.2.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.2.p.1">¶</a></p><ul><li>DAV:comment</li><li>DAV:creator-displayname</li><li>DAV:supported-method-set</li><li>DAV:supported-live-property-set</li><li>DAV:supported-report-set</li><li>all properties defined in WebDAV <a href="#RFC2518" id="rfc.xref.RFC2518.15"><cite title="HTTP Extensions for Distributed Authoring -- WEBDAV">[RFC2518]</cite></a>.</li></ul></div><div id="rfc.section.A.2.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.2.p.2">¶</a></p><ul><li>REPORT</li><li>all methods defined in WebDAV <a href="#RFC2518" id="rfc.xref.RFC2518.16"><cite title="HTTP Extensions for Distributed Authoring -- WEBDAV">[RFC2518]</cite></a></li><li>all methods defined in HTTP/1.1 <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.</li></ul></div></section><section id="n-deltav-compliant-collection"><h3 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a href="#n-deltav-compliant-collection">DeltaV-Compliant Collection</a></h3><div id="rfc.section.A.3.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.3.p.1">¶</a></p><ul><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.3.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.3.p.2">¶</a></p><ul><li>BASELINE-CONTROL (baseline)</li><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-versionable-resource"><h3 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a href="#n-versionable-resource">Versionable Resource</a></h3><div id="rfc.section.A.4.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.4.p.1">¶</a></p><ul><li>DAV:workspace (workspace)</li><li>DAV:version-controlled-configuration (baseline)</li><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.4.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.4.p.2">¶</a></p><ul><li>VERSION-CONTROL</li><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-version-controlled-resource"><h3 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a href="#n-version-controlled-resource">Version-Controlled Resource</a></h3><div id="rfc.section.A.5.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.5.p.1">¶</a></p><ul><li>DAV:auto-version</li><li>DAV:version-history (version-history)</li><li>DAV:workspace (workspace)</li><li>DAV:version-controlled-configuration (baseline)</li><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.5.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.5.p.2">¶</a></p><ul><li>VERSION-CONTROL</li><li>MERGE (merge)</li><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-version"><h3 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a href="#n-version">Version</a></h3><div id="rfc.section.A.6.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.6.p.1">¶</a></p><ul><li>DAV:predecessor-set</li><li>DAV:successor-set</li><li>DAV:checkout-set</li><li>DAV:version-name</li><li>DAV:checkout-fork (in-place-checkout or working resource)</li><li>DAV:checkin-fork (in-place-checkout or working resource)</li><li>DAV:version-history (version-history)</li><li>DAV:label-name-set (label)</li><li>DAV:activity-set (activity)</li><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.6.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.6.p.2">¶</a></p><ul><li>LABEL (label)</li><li>CHECKOUT (working-resource)</li><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-checked-in-version-controlled-resource"><h3 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a href="#n-checked-in-version-controlled-resource">Checked-In Version-Controlled Resource</a></h3><div id="rfc.section.A.7.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.7.p.1">¶</a></p><ul><li>DAV:checked-in</li><li>all version-controlled resource properties.</li></ul></div><div id="rfc.section.A.7.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.7.p.2">¶</a></p><ul><li>CHECKOUT (checkout-in-place)</li><li>UPDATE (update)</li><li>all version-controlled resource methods.</li></ul></div></section><section id="n-checked-out-resource"><h3 id="rfc.section.A.8"><a href="#rfc.section.A.8">A.8</a>&nbsp;<a href="#n-checked-out-resource">Checked-Out Resource</a></h3><div id="rfc.section.A.8.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.8.p.1">¶</a></p><ul><li>DAV:checked-out</li><li>DAV:predecessor-set</li><li>DAV:checkout-fork (in-place-checkout or working resource)</li><li>DAV:checkin-fork (in-place-checkout or working resource)</li><li>DAV:merge-set (merge)</li><li>DAV:auto-merge-set (merge)</li><li>DAV:unreserved (activity)</li><li>DAV:activity-set (activity)</li></ul></div><div id="rfc.section.A.8.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.8.p.2">¶</a></p><ul><li>CHECKIN (checkout-in-place or working-resource)</li><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-checked-out-version-controlled-resource--checkout-in-place-"><h3 id="rfc.section.A.9"><a href="#rfc.section.A.9">A.9</a>&nbsp;<a href="#n-checked-out-version-controlled-resource--checkout-in-place-">Checked-Out Version-Controlled Resource (checkout-in-place)</a></h3><div id="rfc.section.A.9.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.9.p.1">¶</a></p><ul><li>all version-controlled resource properties.</li><li>all checked-out resource properties.</li></ul></div><div id="rfc.section.A.9.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.9.p.2">¶</a></p><ul><li>UNCHECKOUT</li><li>all version-controlled resource methods.</li><li>all checked-out resource methods.</li></ul></div></section><section id="n-working-resource--working-resource-"><h3 id="rfc.section.A.10"><a href="#rfc.section.A.10">A.10</a>&nbsp;<a href="#n-working-resource--working-resource-">Working Resource (working-resource)</a></h3><div id="rfc.section.A.10.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.10.p.1">¶</a></p><ul><li>all DeltaV-compliant resource properties</li><li>all checked-out resource properties</li><li>DAV:auto-update.</li></ul></div><div id="rfc.section.A.10.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.10.p.2">¶</a></p><ul><li>all checked-out resource methods.</li></ul></div></section><section id="n-version-history--version-history-"><h3 id="rfc.section.A.11"><a href="#rfc.section.A.11">A.11</a>&nbsp;<a href="#n-version-history--version-history-">Version History (version-history)</a></h3><div id="rfc.section.A.11.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.11.p.1">¶</a></p><ul><li>DAV:version-set</li><li>DAV:root-version</li><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.11.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.11.p.2">¶</a></p><ul><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-workspace--workspace-"><h3 id="rfc.section.A.12"><a href="#rfc.section.A.12">A.12</a>&nbsp;<a href="#n-workspace--workspace-">Workspace (workspace)</a></h3><div id="rfc.section.A.12.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.12.p.1">¶</a></p><ul><li>DAV:workspace-checkout-set</li><li>DAV:baseline-controlled-collection-set (baseline)</li><li>DAV:current-activity-set (activity)</li><li>all DeltaV-compliant collection properties.</li></ul></div><div id="rfc.section.A.12.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.12.p.2">¶</a></p><ul><li>all DeltaV-compliant collection methods.</li></ul></div></section><section id="n-activity--activity-"><h3 id="rfc.section.A.13"><a href="#rfc.section.A.13">A.13</a>&nbsp;<a href="#n-activity--activity-">Activity (activity)</a></h3><div id="rfc.section.A.13.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.13.p.1">¶</a></p><ul><li>DAV:activity-version-set</li><li>DAV:activity-checkout-set</li><li>DAV:subactivity-set</li><li>DAV:current-workspace-set</li><li>all DeltaV-compliant resource properties.</li></ul></div><div id="rfc.section.A.13.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.13.p.2">¶</a></p><ul><li>all DeltaV-compliant resource methods.</li></ul></div></section><section id="n-version-controlled-collection--version-controlled-collection-"><h3 id="rfc.section.A.14"><a href="#rfc.section.A.14">A.14</a>&nbsp;<a href="#n-version-controlled-collection--version-controlled-collection-">Version-Controlled Collection (version-controlled-collection)</a></h3><div id="rfc.section.A.14.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.14.p.1">¶</a></p><ul><li>DAV:eclipsed-set</li><li>all version-controlled resource properties.</li></ul></div><div id="rfc.section.A.14.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.14.p.2">¶</a></p><ul><li>all version-controlled resource methods.</li></ul></div></section><section id="n-collection-version--version-controlled-collection-"><h3 id="rfc.section.A.15"><a href="#rfc.section.A.15">A.15</a>&nbsp;<a href="#n-collection-version--version-controlled-collection-">Collection Version (version-controlled-collection)</a></h3><div id="rfc.section.A.15.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.15.p.1">¶</a></p><ul><li>DAV:version-controlled-binding-set</li><li>all version properties.</li></ul></div><div id="rfc.section.A.15.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.15.p.2">¶</a></p><ul><li>all version methods.</li></ul></div></section><section id="n-version-controlled-configuration--baseline-"><h3 id="rfc.section.A.16"><a href="#rfc.section.A.16">A.16</a>&nbsp;<a href="#n-version-controlled-configuration--baseline-">Version-Controlled Configuration (baseline)</a></h3><div id="rfc.section.A.16.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.16.p.1">¶</a></p><ul><li>DAV:baseline-controlled-collection</li><li>all version-controlled resource properties.</li></ul></div><div id="rfc.section.A.16.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.16.p.2">¶</a></p><ul><li>all version-controlled resource methods.</li></ul></div></section><section id="n-baseline--baseline-"><h3 id="rfc.section.A.17"><a href="#rfc.section.A.17">A.17</a>&nbsp;<a href="#n-baseline--baseline-">Baseline (baseline)</a></h3><div id="rfc.section.A.17.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.17.p.1">¶</a></p><ul><li>DAV:baseline-collection</li><li>DAV:subbaseline-set</li><li>all version properties.</li></ul></div><div id="rfc.section.A.17.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.17.p.2">¶</a></p><ul><li>all version methods.</li></ul></div></section><section id="n-checked-out-version-controlled-configuration--baseline-"><h3 id="rfc.section.A.18"><a href="#rfc.section.A.18">A.18</a>&nbsp;<a href="#n-checked-out-version-controlled-configuration--baseline-">Checked-Out Version-Controlled Configuration (baseline)</a></h3><div id="rfc.section.A.18.p.1"><p>Supported live properties: <a class="self" href="#rfc.section.A.18.p.1">¶</a></p><ul><li>DAV:subbaseline-set</li><li>all version-controlled configuration properties.</li></ul></div><div id="rfc.section.A.18.p.2"><p>Supported methods: <a class="self" href="#rfc.section.A.18.p.2">¶</a></p><ul><li>all version-controlled configuration methods.</li></ul></div></section></section><hr class="noprint"><section id="rfc.index" class="np"><h2><a href="#rfc.index">Index</a></h2><p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> </p><div class="print2col"><ul class="ind"><li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul><li>Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13"><b>13</b></a></li><li>Activity Resource&nbsp;&nbsp;<a href="#rfc.iref.a.2">10.2</a></li><li>Ancestor&nbsp;&nbsp;<a href="#rfc.iref.a.1">1.3</a></li></ul></li><li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul><li>Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12"><b>12</b></a></li><li>Baseline Resource&nbsp;&nbsp;<a href="#rfc.iref.b.1">10.2</a></li><li>BASELINE-CONTROL method&nbsp;&nbsp;<a href="#rfc.section.12.6"><b>12.6</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.b.3">12.6</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.b.5">12.6</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.b.4">12.6</a></li></ul></li><li>Baseline-Controlled Collection&nbsp;&nbsp;<a href="#rfc.iref.b.2">10.2</a></li></ul></li><li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul><li>Checked-In&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.3</a></li><li>Checked-Out&nbsp;&nbsp;<a href="#rfc.iref.c.2">1.3</a></li><li>Checked-Out Resource&nbsp;&nbsp;<a href="#rfc.iref.c.3">1.3</a></li><li>CHECKIN method&nbsp;&nbsp;<ul><li>(applied to a version-controlled resource)&nbsp;&nbsp;<a href="#rfc.section.4.4"><b>4.4</b></a></li><li>(applied to a working resource)&nbsp;&nbsp;<a href="#rfc.section.9.4"><b>9.4</b></a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.c.62">5.10</a>, <a href="#rfc.iref.c.155">12.12</a>, <a href="#rfc.iref.c.188">13.11</a>, <a href="#rfc.iref.c.201">14.10</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.c.136">11.6</a>, <a href="#rfc.iref.c.151">12.12</a>, <a href="#rfc.iref.c.185">13.11</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.11">13.11</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.12">12.12</a></li><li>additional semantics with Merge Feature&nbsp;&nbsp;<a href="#rfc.section.11.6">11.6</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.10">14.10</a></li><li>additional semantics with Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5.10">5.10</a></li><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.c.41">4.4</a>, <a href="#rfc.iref.c.109">9.4</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.c.47">4.4</a>, <a href="#rfc.iref.c.116">9.4</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.c.42">4.4</a>, <a href="#rfc.iref.c.110">9.4</a></li></ul></li><li>CHECKOUT method&nbsp;&nbsp;<ul><li>(applied to a version)&nbsp;&nbsp;<a href="#rfc.section.9.3"><b>9.3</b></a></li><li>(applied to a version-controlled resource)&nbsp;&nbsp;<a href="#rfc.section.4.3"><b>4.3</b></a></li><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.c.91">8.8</a>, <a href="#rfc.iref.c.178">13.10</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.c.95">8.8</a>, <a href="#rfc.iref.c.182">13.10</a>, <a href="#rfc.iref.c.199">14.9</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.c.92">8.8</a>, <a href="#rfc.iref.c.149">12.11</a>, <a href="#rfc.iref.c.179">13.10</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.10">13.10</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.11">12.11</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.8"><b>8.8</b></a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.9">14.9</a></li><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.c.31">4.3</a>, <a href="#rfc.iref.c.100">9.3</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.c.38">4.3</a>, <a href="#rfc.iref.c.106">9.3</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.c.32">4.3</a>, <a href="#rfc.iref.c.101">9.3</a></li></ul></li><li>Collection&nbsp;&nbsp;<a href="#rfc.iref.c.125">10.2</a></li><li>Collection Version Resource&nbsp;&nbsp;<a href="#rfc.iref.c.126">10.2</a></li><li>Condition Names&nbsp;&nbsp;<ul><li>DAV:activity-checkin (post)&nbsp;&nbsp;<a href="#rfc.iref.c.190"><b>13.11</b></a></li><li>DAV:activity-location-ok (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.171"><b>13.5</b></a></li><li>DAV:add-must-be-new-label (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.78"><b>8.2</b></a></li><li>DAV:add-or-set-label (post)&nbsp;&nbsp;<a href="#rfc.iref.c.80"><b>8.2</b></a></li><li>DAV:add-to-history (post)&nbsp;&nbsp;<a href="#rfc.iref.c.63"><b>5.10</b></a></li><li>DAV:ancestor-version (post)&nbsp;&nbsp;<a href="#rfc.iref.c.130"><b>11.2</b></a></li><li>DAV:apply-request-to-labeled-version (post)&nbsp;&nbsp;<a href="#rfc.iref.c.83"><b>8.5</b></a>, <a href="#rfc.iref.c.85"><b>8.6</b></a>, <a href="#rfc.iref.c.90"><b>8.7</b></a>, <a href="#rfc.iref.c.96"><b>8.8</b></a>, <a href="#rfc.iref.c.99"><b>8.9</b></a></li><li>DAV:atomic-activity-checkin (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.187"><b>13.11</b></a></li><li>DAV:auto-checkin (post)&nbsp;&nbsp;<a href="#rfc.iref.c.30"><b>3.16</b></a></li><li>DAV:auto-checkout (post)&nbsp;&nbsp;<a href="#rfc.iref.c.10"><b>3.10</b></a>, <a href="#rfc.iref.c.17"><b>3.12</b></a>, <a href="#rfc.iref.c.24">3.14</a></li><li>DAV:auto-checkout-checkin (post)&nbsp;&nbsp;<a href="#rfc.iref.c.11"><b>3.10</b></a>, <a href="#rfc.iref.c.18"><b>3.12</b></a>, <a href="#rfc.iref.c.25">3.14</a></li><li>DAV:auto-update (post)&nbsp;&nbsp;<a href="#rfc.iref.c.119"><b>9.4</b></a></li><li>DAV:baseline-controlled-members-must-be-checked-in (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.158"><b>12.13</b></a></li><li>DAV:baselines-from-same-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.147"><b>12.7</b></a></li><li>DAV:cancel-checked-out (post)&nbsp;&nbsp;<a href="#rfc.iref.c.53"><b>4.5</b></a></li><li>DAV:cannot-add-to-existing-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.70"><b>6.7</b></a></li><li>DAV:cannot-copy-collection-version (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.194"><b>14.6</b></a></li><li>DAV:cannot-copy-history (post)&nbsp;&nbsp;<a href="#rfc.iref.c.59"><b>5.7</b></a></li><li>DAV:cannot-merge-checked-out-resource (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.128"><b>11.2</b></a></li><li>DAV:cannot-modify-checked-in-parent (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.192"><b>14.4</b></a>, <a href="#rfc.iref.c.195"><b>14.7</b></a>, <a href="#rfc.iref.c.197"><b>14.8</b></a></li><li>DAV:cannot-modify-destination-checked-in-parent (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.196"><b>14.7</b></a></li><li>DAV:cannot-modify-protected-property (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.15"><b>3.12</b></a></li><li>DAV:cannot-modify-version (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b>3.10</b></a>, <a href="#rfc.iref.c.14">3.12</a></li><li>DAV:cannot-modify-version-controlled-configuration (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.154"><b>12.12</b></a>, <a href="#rfc.iref.c.160"><b>12.13</b></a>, <a href="#rfc.iref.c.165"><b>12.14</b></a></li><li>DAV:cannot-modify-version-controlled-content (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>3.10</b></a></li><li>DAV:cannot-modify-version-controlled-property (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.13"><b>3.12</b></a></li><li>DAV:cannot-rename-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.60"><b>5.8</b></a></li><li>DAV:cannot-rename-version (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.27"><b>3.15</b></a></li><li>DAV:cannot-rename-working-resource (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.123"><b>9.7</b></a></li><li>DAV:checked-in (post)&nbsp;&nbsp;<a href="#rfc.iref.c.50"><b>4.4</b></a></li><li>DAV:checked-out-for-merge (post)&nbsp;&nbsp;<a href="#rfc.iref.c.132"><b>11.2</b></a></li><li>DAV:checkin-activity (post)&nbsp;&nbsp;<a href="#rfc.iref.c.191"><b>13.12</b></a></li><li>DAV:checkin-fork-discouraged (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.46"><b>4.4</b></a>, <a href="#rfc.iref.c.114">9.4</a></li><li>DAV:checkin-fork-forbidden (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.45"><b>4.4</b></a>, <a href="#rfc.iref.c.113">9.4</a></li><li>DAV:checkout-not-allowed (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.129"><b>11.2</b></a></li><li>DAV:checkout-of-checked-out-version-is-discouraged (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.37"><b>4.3</b></a>, <a href="#rfc.iref.c.105">9.3</a></li><li>DAV:checkout-of-checked-out-version-is-forbidden (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.36"><b>4.3</b></a>, <a href="#rfc.iref.c.104">9.3</a></li><li>DAV:checkout-of-version-with-descendant-is-discouraged (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.35"><b>4.3</b></a>, <a href="#rfc.iref.c.103">9.3</a></li><li>DAV:checkout-of-version-with-descendant-is-forbidden (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.34"><b>4.3</b></a>, <a href="#rfc.iref.c.102">9.3</a></li><li>DAV:copy-creates-new-resource (post)&nbsp;&nbsp;<a href="#rfc.iref.c.26"><b>3.14</b></a>, <a href="#rfc.iref.c.122"><b>9.6</b></a></li><li>DAV:create-baseline-collection (post)&nbsp;&nbsp;<a href="#rfc.iref.c.156"><b>12.12</b></a></li><li>DAV:create-new-baseline (post)&nbsp;&nbsp;<a href="#rfc.iref.c.145"><b>12.6</b></a></li><li>DAV:create-version (post)&nbsp;&nbsp;<a href="#rfc.iref.c.48"><b>4.4</b></a>, <a href="#rfc.iref.c.117">9.4</a></li><li>DAV:create-version-controlled-configuration (post)&nbsp;&nbsp;<a href="#rfc.iref.c.142"><b>12.6</b></a></li><li>DAV:create-working-resource (post)&nbsp;&nbsp;<a href="#rfc.iref.c.107"><b>9.3</b></a></li><li>DAV:create-working-resource-from-checked-in-version (post)&nbsp;&nbsp;<a href="#rfc.iref.c.108"><b>9.3</b></a></li><li>DAV:delete-activity-reference (post)&nbsp;&nbsp;<a href="#rfc.iref.c.174"><b>13.8</b></a></li><li>DAV:delete-version-reference (post)&nbsp;&nbsp;<a href="#rfc.iref.c.135"><b>11.5</b></a></li><li>DAV:delete-version-set (post)&nbsp;&nbsp;<a href="#rfc.iref.c.56"><b>5.6</b></a></li><li>DAV:delete-working-resource (post)&nbsp;&nbsp;<a href="#rfc.iref.c.120"><b>9.4</b></a></li><li>DAV:delete-workspace-members (post)&nbsp;&nbsp;<a href="#rfc.iref.c.67"><b>6.5</b></a></li><li>DAV:depth-update (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.98"><b>8.9</b></a></li><li>DAV:descendant-version (post)&nbsp;&nbsp;<a href="#rfc.iref.c.131"><b>11.2</b></a></li><li>DAV:initialize-activity (post)&nbsp;&nbsp;<a href="#rfc.iref.c.172"><b>13.5</b></a></li><li>DAV:initialize-activity-set (post)&nbsp;&nbsp;<a href="#rfc.iref.c.183"><b>13.10</b></a>, <a href="#rfc.iref.c.189"><b>13.11</b></a></li><li>DAV:initialize-predecessor-set (post)&nbsp;&nbsp;<a href="#rfc.iref.c.40"><b>4.3</b></a></li><li>DAV:initialize-unreserved (post)&nbsp;&nbsp;<a href="#rfc.iref.c.184"><b>13.10</b></a></li><li>DAV:initialize-version-content-and-properties (post)&nbsp;&nbsp;<a href="#rfc.iref.c.49"><b>4.4</b></a>, <a href="#rfc.iref.c.118">9.4</a></li><li>DAV:initialize-version-controlled-bindings (post)&nbsp;&nbsp;<a href="#rfc.iref.c.202"><b>14.10</b></a></li><li>DAV:initialize-version-history-bindings (post)&nbsp;&nbsp;<a href="#rfc.iref.c.200"><b>14.9</b></a></li><li>DAV:initialize-workspace (post)&nbsp;&nbsp;<a href="#rfc.iref.c.66"><b>6.3</b></a></li><li>DAV:is-checked-out (post)&nbsp;&nbsp;<a href="#rfc.iref.c.39"><b>4.3</b></a></li><li>DAV:keep-checked-out (post)&nbsp;&nbsp;<a href="#rfc.iref.c.51"><b>4.4</b></a></li><li>DAV:label-must-exist (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.79"><b>8.2</b></a></li><li>DAV:linear-activity (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.181"><b>13.10</b></a>, <a href="#rfc.iref.c.186"><b>13.11</b></a></li><li>DAV:merge-baseline (post)&nbsp;&nbsp;<a href="#rfc.iref.c.166"><b>12.14</b></a></li><li>DAV:merge-must-be-complete (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.137"><b>11.6</b></a></li><li>DAV:merge-subbaselines (post)&nbsp;&nbsp;<a href="#rfc.iref.c.167"><b>12.14</b></a></li><li>DAV:modify-configuration (post)&nbsp;&nbsp;<a href="#rfc.iref.c.157"><b>12.12</b></a>, <a href="#rfc.iref.c.163"><b>12.13</b></a>, <a href="#rfc.iref.c.169"><b>12.14</b></a></li><li>DAV:must-be-activity (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.173"><b>13.6</b></a></li><li>DAV:must-be-baseline (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.139"><b>12.6</b></a>, <a href="#rfc.iref.c.146"><b>12.7</b></a></li><li>DAV:must-be-checked-in (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.33"><b>4.3</b></a>, <a href="#rfc.iref.c.76"><b>8.2</b></a></li><li>DAV:must-be-checked-out (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.43"><b>4.4</b></a>, <a href="#rfc.iref.c.111">9.4</a></li><li>DAV:must-be-checked-out-version-controlled-resource (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.52"><b>4.5</b></a></li><li>DAV:must-be-version (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.71"><b>6.7</b></a></li><li>DAV:must-be-version-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.55"><b>5.4</b></a></li><li>DAV:must-have-no-version-controlled-members (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.140"><b>12.6</b></a></li><li>DAV:must-not-change-existing-checked-in-out (post)&nbsp;&nbsp;<a href="#rfc.iref.c.5"><b>3.5</b></a></li><li>DAV:must-not-copy-versioning-property (post)&nbsp;&nbsp;<a href="#rfc.iref.c.23"><b>3.14</b></a></li><li>DAV:must-not-have-label-and-apply-to-version (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.94"><b>8.8</b></a></li><li>DAV:must-not-update-baseline-collection (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.150"><b>12.11</b></a>, <a href="#rfc.iref.c.159"><b>12.13</b></a>, <a href="#rfc.iref.c.164"><b>12.14</b></a></li><li>DAV:must-select-version-in-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.77"><b>8.2</b></a>, <a href="#rfc.iref.c.82"><b>8.5</b></a>, <a href="#rfc.iref.c.84"><b>8.6</b></a>, <a href="#rfc.iref.c.88"><b>8.7</b></a>, <a href="#rfc.iref.c.93"><b>8.8</b></a>, <a href="#rfc.iref.c.97"><b>8.9</b></a></li><li>DAV:new-version-controlled-collection (post)&nbsp;&nbsp;<a href="#rfc.iref.c.198"><b>14.8</b></a></li><li>DAV:new-version-controlled-resource (post)&nbsp;&nbsp;<a href="#rfc.iref.c.73"><b>6.7</b></a></li><li>DAV:new-version-history (post)&nbsp;&nbsp;<a href="#rfc.iref.c.61"><b>5.9</b></a></li><li>DAV:no-checked-out-baseline-controlled-collection-members (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.152"><b>12.12</b></a></li><li>DAV:no-modification (post)&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>3.6</b></a></li><li>DAV:no-overwrite-by-auto-update (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.115"><b>9.4</b></a></li><li>DAV:no-version-delete (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.19"><b>3.13</b></a></li><li>DAV:one-baseline-controlled-collection-per-history-per-workspace (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.141"><b>12.6</b></a></li><li>DAV:one-checkout-per-activity-per-history (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.180"><b>13.10</b></a></li><li>DAV:one-version-controlled-resource-per-history-per-workspace (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.72"><b>6.7</b></a></li><li>DAV:one-version-per-history-per-baseline (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.153"><b>12.12</b></a></li><li>DAV:preserve-versioning-properties (post)&nbsp;&nbsp;<a href="#rfc.iref.c.28"><b>3.15</b></a></li><li>DAV:put-under-version-control (post)&nbsp;&nbsp;<a href="#rfc.iref.c.4"><b>3.5</b></a></li><li>DAV:reference-version-controlled-configuration (post)&nbsp;&nbsp;<a href="#rfc.iref.c.143"><b>12.6</b></a></li><li>DAV:remove-label (post)&nbsp;&nbsp;<a href="#rfc.iref.c.81"><b>8.2</b></a></li><li>DAV:report-properties (post)&nbsp;&nbsp;<a href="#rfc.iref.c.75"><b>7.1</b></a>, <a href="#rfc.iref.c.134"><b>11.2</b></a></li><li>DAV:resource-must-be-null (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.64"><b>6.3</b></a>, <a href="#rfc.iref.c.170"><b>13.5</b></a></li><li>DAV:restore-content-and-dead-properties (post)&nbsp;&nbsp;<a href="#rfc.iref.c.54"><b>4.5</b></a></li><li>DAV:select-existing-baseline (post)&nbsp;&nbsp;<a href="#rfc.iref.c.144"><b>12.6</b></a></li><li>DAV:set-baseline-controlled-collection-members (post)&nbsp;&nbsp;<a href="#rfc.iref.c.161"><b>12.13</b></a>, <a href="#rfc.iref.c.168"><b>12.14</b></a></li><li>DAV:supported-live-property (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.12"><b>3.11</b></a>, <a href="#rfc.iref.c.16"><b>3.12</b></a></li><li>DAV:supported-report (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.6"><b>3.6</b></a></li><li>DAV:update-activity-reference (post)&nbsp;&nbsp;<a href="#rfc.iref.c.176"><b>13.9</b></a></li><li>DAV:update-auto-update (post)&nbsp;&nbsp;<a href="#rfc.iref.c.124"><b>9.7</b></a></li><li>DAV:update-checked-out-reference (post)&nbsp;&nbsp;<a href="#rfc.iref.c.175"><b>13.9</b></a></li><li>DAV:update-content-and-properties (post)&nbsp;&nbsp;<a href="#rfc.iref.c.74"><b>7.1</b></a></li><li>DAV:update-merge-set (post)&nbsp;&nbsp;<a href="#rfc.iref.c.133"><b>11.2</b></a></li><li>DAV:update-predecessor-set (post)&nbsp;&nbsp;<a href="#rfc.iref.c.20"><b>3.13</b></a></li><li>DAV:update-subbaselines (post)&nbsp;&nbsp;<a href="#rfc.iref.c.162"><b>12.13</b></a></li><li>DAV:update-version-controlled-collection-members (post)&nbsp;&nbsp;<a href="#rfc.iref.c.204"><b>14.11</b></a></li><li>DAV:update-workspace-reference (post)&nbsp;&nbsp;<a href="#rfc.iref.c.177"><b>13.9</b></a></li><li>DAV:version-control-working-collection-members (post)&nbsp;&nbsp;<a href="#rfc.iref.c.203"><b>14.10</b></a></li><li>DAV:version-controlled-configuration-must-not-exist (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.138"><b>12.6</b></a></li><li>DAV:version-history-has-root (post)&nbsp;&nbsp;<a href="#rfc.iref.c.57"><b>5.6</b></a></li><li>DAV:version-history-is-tree (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.29"><b>3.16</b></a>, <a href="#rfc.iref.c.44"><b>4.4</b></a>, <a href="#rfc.iref.c.112">9.4</a></li><li>DAV:workspace-location-ok (pre)&nbsp;&nbsp;<a href="#rfc.iref.c.65"><b>6.3</b></a></li><li>DAV:workspace-member-moved (post)&nbsp;&nbsp;<a href="#rfc.iref.c.68"><b>6.6</b></a></li><li>DAV:workspace-moved (post)&nbsp;&nbsp;<a href="#rfc.iref.c.69"><b>6.6</b></a></li></ul></li><li>Configuration&nbsp;&nbsp;<a href="#rfc.iref.c.127">10.2</a></li><li>COPY method&nbsp;&nbsp;<ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.c.86">8.7</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.c.22">3.14</a>, <a href="#rfc.iref.c.89">8.7</a>, <a href="#rfc.iref.c.121">9.6</a>, <a href="#rfc.iref.c.148">12.10</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.c.21">3.14</a>, <a href="#rfc.iref.c.58">5.7</a>, <a href="#rfc.iref.c.87">8.7</a>, <a href="#rfc.iref.c.193">14.6</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.10">12.10</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.7">8.7</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.14">3.14</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.6">14.6</a></li><li>additional semantics with Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5.7">5.7</a></li><li>additional semantics with Working-Resource Feature&nbsp;&nbsp;<a href="#rfc.section.9.6">9.6</a></li></ul></li></ul></li><li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul><li>DAV header&nbsp;&nbsp;<ul><li>compliance class 'activity'&nbsp;&nbsp;<a href="#rfc.section.13.7"><b>13.7</b></a></li><li>compliance class 'baseline'&nbsp;&nbsp;<a href="#rfc.section.12.8"><b>12.8</b></a></li><li>compliance class 'checkout-in-place'&nbsp;&nbsp;<a href="#rfc.section.4.6"><b>4.6</b></a></li><li>compliance class 'label'&nbsp;&nbsp;<a href="#rfc.section.8.4"><b>8.4</b></a></li><li>compliance class 'merge'&nbsp;&nbsp;<a href="#rfc.section.11.4"><b>11.4</b></a></li><li>compliance class 'update'&nbsp;&nbsp;<a href="#rfc.section.7.2"><b>7.2</b></a></li><li>compliance class 'version-control'&nbsp;&nbsp;<a href="#rfc.section.3.9"><b>3.9</b></a></li><li>compliance class 'version-controlled-collection'&nbsp;&nbsp;<a href="#rfc.section.14.3"><b>14.3</b></a></li><li>compliance class 'version-history'&nbsp;&nbsp;<a href="#rfc.section.5.5"><b>5.5</b></a></li><li>compliance class 'working-resource'&nbsp;&nbsp;<a href="#rfc.section.9.5"><b>9.5</b></a></li><li>compliance class 'workspace'&nbsp;&nbsp;<a href="#rfc.section.6.4"><b>6.4</b></a></li></ul></li><li>DAV:activity resource type&nbsp;&nbsp;<a href="#rfc.section.13.1"><b>13.1</b></a></li><li>DAV:activity-checkin postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.167"><b>13.11</b></a></li><li>DAV:activity-checkout-set property&nbsp;&nbsp;<a href="#rfc.section.13.1.2"><b>13.1.2</b></a></li><li>DAV:activity-location-ok precondition&nbsp;&nbsp;<a href="#rfc.iref.d.150"><b>13.5</b></a></li><li>DAV:activity-set property&nbsp;&nbsp;<a href="#rfc.section.13.2.1"><b>13.2.1</b></a>, <a href="#rfc.section.13.3.2"><b>13.3.2</b></a></li><li>DAV:activity-version-set property&nbsp;&nbsp;<a href="#rfc.section.13.1.1"><b>13.1.1</b></a></li><li>DAV:add-must-be-new-label precondition&nbsp;&nbsp;<a href="#rfc.iref.d.74"><b>8.2</b></a></li><li>DAV:add-or-set-label postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.76"><b>8.2</b></a></li><li>DAV:add-to-history postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.58"><b>5.10</b></a></li><li>DAV:ancestor-version postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.110"><b>11.2</b></a></li><li>DAV:apply-request-to-labeled-version postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.79"><b>8.5</b></a>, <a href="#rfc.iref.d.81"><b>8.6</b></a>, <a href="#rfc.iref.d.83"><b>8.7</b></a>, <a href="#rfc.iref.d.86"><b>8.8</b></a>, <a href="#rfc.iref.d.89"><b>8.9</b></a></li><li>DAV:atomic-activity-checkin precondition&nbsp;&nbsp;<a href="#rfc.iref.d.165"><b>13.11</b></a></li><li>DAV:auto-checkin postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.30"><b>3.16</b></a></li><li>DAV:auto-checkout postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.10"><b>3.10</b></a>, <a href="#rfc.iref.d.17"><b>3.12</b></a>, <a href="#rfc.iref.d.24">3.14</a></li><li>DAV:auto-checkout-checkin postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.11"><b>3.10</b></a>, <a href="#rfc.iref.d.18"><b>3.12</b></a>, <a href="#rfc.iref.d.25">3.14</a></li><li>DAV:auto-merge-set property&nbsp;&nbsp;<a href="#rfc.section.11.1.2"><b>11.1.2</b></a></li><li>DAV:auto-update postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.103"><b>9.4</b></a></li><li>DAV:auto-update property&nbsp;&nbsp;<a href="#rfc.section.9.2.1"><b>9.2.1</b></a></li><li>DAV:auto-version property&nbsp;&nbsp;<a href="#rfc.section.3.2.2"><b>3.2.2</b></a></li><li>DAV:baseline resource type&nbsp;&nbsp;<a href="#rfc.section.12.3"><b>12.3</b></a></li><li>DAV:baseline-collection property&nbsp;&nbsp;<a href="#rfc.section.12.3.1"><b>12.3.1</b></a></li><li>DAV:baseline-controlled-collection property&nbsp;&nbsp;<a href="#rfc.section.12.1.1"><b>12.1.1</b></a></li><li>DAV:baseline-controlled-collection-set property&nbsp;&nbsp;<a href="#rfc.section.12.5.1"><b>12.5.1</b></a></li><li>DAV:baseline-controlled-members-must-be-checked-in precondition&nbsp;&nbsp;<a href="#rfc.iref.d.137"><b>12.13</b></a></li><li>DAV:baselines-from-same-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.130"><b>12.7</b></a></li><li>DAV:cancel-checked-out postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.47"><b>4.5</b></a></li><li>DAV:cannot-add-to-existing-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.66"><b>6.7</b></a></li><li>DAV:cannot-copy-collection-version precondition&nbsp;&nbsp;<a href="#rfc.iref.d.171"><b>14.6</b></a></li><li>DAV:cannot-copy-history postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.55"><b>5.7</b></a></li><li>DAV:cannot-merge-checked-out-resource precondition&nbsp;&nbsp;<a href="#rfc.iref.d.108"><b>11.2</b></a></li><li>DAV:cannot-modify-checked-in-parent precondition&nbsp;&nbsp;<a href="#rfc.iref.d.170"><b>14.4</b></a>, <a href="#rfc.iref.d.172"><b>14.7</b></a>, <a href="#rfc.iref.d.174"><b>14.8</b></a></li><li>DAV:cannot-modify-destination-checked-in-parent precondition&nbsp;&nbsp;<a href="#rfc.iref.d.173"><b>14.7</b></a></li><li>DAV:cannot-modify-protected-property precondition&nbsp;&nbsp;<a href="#rfc.iref.d.15"><b>3.12</b></a></li><li>DAV:cannot-modify-version precondition&nbsp;&nbsp;<a href="#rfc.iref.d.9"><b>3.10</b></a>, <a href="#rfc.iref.d.14">3.12</a></li><li>DAV:cannot-modify-version-controlled-configuration precondition&nbsp;&nbsp;<a href="#rfc.iref.d.134"><b>12.12</b></a>, <a href="#rfc.iref.d.139"><b>12.13</b></a>, <a href="#rfc.iref.d.144"><b>12.14</b></a></li><li>DAV:cannot-modify-version-controlled-content precondition&nbsp;&nbsp;<a href="#rfc.iref.d.8"><b>3.10</b></a></li><li>DAV:cannot-modify-version-controlled-property precondition&nbsp;&nbsp;<a href="#rfc.iref.d.13"><b>3.12</b></a></li><li>DAV:cannot-rename-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.56"><b>5.8</b></a></li><li>DAV:cannot-rename-version precondition&nbsp;&nbsp;<a href="#rfc.iref.d.27"><b>3.15</b></a></li><li>DAV:cannot-rename-working-resource precondition&nbsp;&nbsp;<a href="#rfc.iref.d.106"><b>9.7</b></a></li><li>DAV:checked-in postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.44"><b>4.4</b></a></li><li>DAV:checked-in property&nbsp;&nbsp;<a href="#rfc.section.3.2.1"><b>3.2.1</b></a></li><li>DAV:checked-out property&nbsp;&nbsp;<a href="#rfc.section.3.3.1"><b>3.3.1</b></a></li><li>DAV:checked-out-for-merge postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.112"><b>11.2</b></a></li><li>DAV:checkin-activity postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.168"><b>13.12</b></a></li><li>DAV:checkin-fork property&nbsp;&nbsp;<a href="#rfc.section.4.1.2"><b>4.1.2</b></a>, <a href="#rfc.section.4.2.2"><b>4.2.2</b></a>, <a href="#rfc.section.9.1.2">9.1.2</a>, <a href="#rfc.section.9.2.3">9.2.3</a></li><li>DAV:checkin-fork-discouraged precondition&nbsp;&nbsp;<a href="#rfc.iref.d.41"><b>4.4</b></a>, <a href="#rfc.iref.d.99">9.4</a></li><li>DAV:checkin-fork-forbidden precondition&nbsp;&nbsp;<a href="#rfc.iref.d.40"><b>4.4</b></a>, <a href="#rfc.iref.d.98">9.4</a></li><li>DAV:checkout-fork property&nbsp;&nbsp;<a href="#rfc.section.4.1.1"><b>4.1.1</b></a>, <a href="#rfc.section.4.2.1"><b>4.2.1</b></a>, <a href="#rfc.section.9.1.1">9.1.1</a>, <a href="#rfc.section.9.2.2">9.2.2</a></li><li>DAV:checkout-not-allowed precondition&nbsp;&nbsp;<a href="#rfc.iref.d.109"><b>11.2</b></a></li><li>DAV:checkout-of-checked-out-version-is-discouraged precondition&nbsp;&nbsp;<a href="#rfc.iref.d.35"><b>4.3</b></a>, <a href="#rfc.iref.d.93">9.3</a></li><li>DAV:checkout-of-checked-out-version-is-forbidden precondition&nbsp;&nbsp;<a href="#rfc.iref.d.34"><b>4.3</b></a>, <a href="#rfc.iref.d.92">9.3</a></li><li>DAV:checkout-of-version-with-descendant-is-discouraged precondition&nbsp;&nbsp;<a href="#rfc.iref.d.33"><b>4.3</b></a>, <a href="#rfc.iref.d.91">9.3</a></li><li>DAV:checkout-of-version-with-descendant-is-forbidden precondition&nbsp;&nbsp;<a href="#rfc.iref.d.32"><b>4.3</b></a>, <a href="#rfc.iref.d.90">9.3</a></li><li>DAV:checkout-set property&nbsp;&nbsp;<a href="#rfc.section.3.4.3"><b>3.4.3</b></a></li><li>DAV:comment property&nbsp;&nbsp;<a href="#rfc.section.3.1.1"><b>3.1.1</b></a></li><li>DAV:compare-baseline report&nbsp;&nbsp;<a href="#rfc.section.12.7"><b>12.7</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.127">12.7</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.d.128">12.7</a></li></ul></li><li>DAV:copy-creates-new-resource postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.26"><b>3.14</b></a>, <a href="#rfc.iref.d.105"><b>9.6</b></a></li><li>DAV:create-baseline-collection postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.135"><b>12.12</b></a></li><li>DAV:create-new-baseline postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.126"><b>12.6</b></a></li><li>DAV:create-version postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.42"><b>4.4</b></a>, <a href="#rfc.iref.d.101">9.4</a></li><li>DAV:create-version-controlled-configuration postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.123"><b>12.6</b></a></li><li>DAV:create-working-resource postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.94"><b>9.3</b></a></li><li>DAV:create-working-resource-from-checked-in-version postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.95"><b>9.3</b></a></li><li>DAV:creator-displayname property&nbsp;&nbsp;<a href="#rfc.section.3.1.2"><b>3.1.2</b></a></li><li>DAV:current-activity-set property&nbsp;&nbsp;<a href="#rfc.section.13.4.1"><b>13.4.1</b></a></li><li>DAV:current-workspace-set property&nbsp;&nbsp;<a href="#rfc.section.13.1.4"><b>13.1.4</b></a></li><li>DAV:delete-activity-reference postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.156"><b>13.8</b></a></li><li>DAV:delete-version-reference postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.117"><b>11.5</b></a></li><li>DAV:delete-version-set postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.53"><b>5.6</b></a></li><li>DAV:delete-working-resource postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.104"><b>9.4</b></a></li><li>DAV:delete-workspace-members postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.63"><b>6.5</b></a></li><li>DAV:depth-update precondition&nbsp;&nbsp;<a href="#rfc.iref.d.88"><b>8.9</b></a></li><li>DAV:descendant-version postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.111"><b>11.2</b></a></li><li>DAV:eclipsed-set property&nbsp;&nbsp;<a href="#rfc.section.14.1.1"><b>14.1.1</b></a></li><li>DAV:expand-property report&nbsp;&nbsp;<a href="#rfc.section.3.8"><b>3.8</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.7">3.8</a></li></ul></li><li>DAV:initialize-activity postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.151"><b>13.5</b></a></li><li>DAV:initialize-activity-set postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.162"><b>13.10</b></a>, <a href="#rfc.iref.d.166"><b>13.11</b></a></li><li>DAV:initialize-predecessor-set postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.37"><b>4.3</b></a></li><li>DAV:initialize-unreserved postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.163"><b>13.10</b></a></li><li>DAV:initialize-version-content-and-properties postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.43"><b>4.4</b></a>, <a href="#rfc.iref.d.102">9.4</a></li><li>DAV:initialize-version-controlled-bindings postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.177"><b>14.10</b></a></li><li>DAV:initialize-version-history-bindings postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.176"><b>14.9</b></a></li><li>DAV:initialize-workspace postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.61"><b>6.3</b></a></li><li>DAV:is-checked-out postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.36"><b>4.3</b></a></li><li>DAV:keep-checked-out postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.45"><b>4.4</b></a></li><li>DAV:label-must-exist precondition&nbsp;&nbsp;<a href="#rfc.iref.d.75"><b>8.2</b></a></li><li>DAV:label-name-set property&nbsp;&nbsp;<a href="#rfc.section.8.1.1"><b>8.1.1</b></a></li><li>DAV:latest-activity-version report&nbsp;&nbsp;<a href="#rfc.section.13.6"><b>13.6</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.152">13.6</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.d.153">13.6</a></li></ul></li><li>DAV:linear-activity precondition&nbsp;&nbsp;<a href="#rfc.iref.d.161"><b>13.10</b></a>, <a href="#rfc.iref.d.164"><b>13.11</b></a></li><li>DAV:locate-by-history report&nbsp;&nbsp;<a href="#rfc.section.5.4"><b>5.4</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.49">5.4</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.d.50">5.4</a></li></ul></li><li>DAV:merge-baseline postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.145"><b>12.14</b></a></li><li>DAV:merge-must-be-complete precondition&nbsp;&nbsp;<a href="#rfc.iref.d.118"><b>11.6</b></a></li><li>DAV:merge-preview report&nbsp;&nbsp;<a href="#rfc.section.11.3"><b>11.3</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.115">11.3</a></li></ul></li><li>DAV:merge-set property&nbsp;&nbsp;<a href="#rfc.section.11.1.1"><b>11.1.1</b></a></li><li>DAV:merge-subbaselines postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.146"><b>12.14</b></a></li><li>DAV:modify-configuration postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.136"><b>12.12</b></a>, <a href="#rfc.iref.d.142"><b>12.13</b></a>, <a href="#rfc.iref.d.148"><b>12.14</b></a></li><li>DAV:must-be-activity precondition&nbsp;&nbsp;<a href="#rfc.iref.d.154"><b>13.6</b></a></li><li>DAV:must-be-baseline precondition&nbsp;&nbsp;<a href="#rfc.iref.d.120"><b>12.6</b></a>, <a href="#rfc.iref.d.129"><b>12.7</b></a></li><li>DAV:must-be-checked-in precondition&nbsp;&nbsp;<a href="#rfc.iref.d.31"><b>4.3</b></a>, <a href="#rfc.iref.d.72"><b>8.2</b></a></li><li>DAV:must-be-checked-out precondition&nbsp;&nbsp;<a href="#rfc.iref.d.38"><b>4.4</b></a>, <a href="#rfc.iref.d.96">9.4</a></li><li>DAV:must-be-checked-out-version-controlled-resource precondition&nbsp;&nbsp;<a href="#rfc.iref.d.46"><b>4.5</b></a></li><li>DAV:must-be-version precondition&nbsp;&nbsp;<a href="#rfc.iref.d.67"><b>6.7</b></a></li><li>DAV:must-be-version-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.51"><b>5.4</b></a></li><li>DAV:must-have-no-version-controlled-members precondition&nbsp;&nbsp;<a href="#rfc.iref.d.121"><b>12.6</b></a></li><li>DAV:must-not-change-existing-checked-in-out postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.3"><b>3.5</b></a></li><li>DAV:must-not-copy-versioning-property postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.23"><b>3.14</b></a></li><li>DAV:must-not-have-label-and-apply-to-versionprecondition&nbsp;&nbsp;<a href="#rfc.iref.d.85"><b>8.8</b></a></li><li>DAV:must-not-update-baseline-collection precondition&nbsp;&nbsp;<a href="#rfc.iref.d.131"><b>12.11</b></a>, <a href="#rfc.iref.d.138"><b>12.13</b></a>, <a href="#rfc.iref.d.143"><b>12.14</b></a></li><li>DAV:must-select-version-in-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.73"><b>8.2</b></a>, <a href="#rfc.iref.d.78"><b>8.5</b></a>, <a href="#rfc.iref.d.80"><b>8.6</b></a>, <a href="#rfc.iref.d.82"><b>8.7</b></a>, <a href="#rfc.iref.d.84"><b>8.8</b></a>, <a href="#rfc.iref.d.87"><b>8.9</b></a></li><li>DAV:new-version-controlled-collection postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.175"><b>14.8</b></a></li><li>DAV:new-version-controlled-resource postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.69"><b>6.7</b></a></li><li>DAV:new-version-history postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.57"><b>5.9</b></a></li><li>DAV:no-checked-out-baseline-controlled-collection-members precondition&nbsp;&nbsp;<a href="#rfc.iref.d.132"><b>12.12</b></a></li><li>DAV:no-modification postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.5"><b>3.6</b></a></li><li>DAV:no-overwrite-by-auto-update precondition&nbsp;&nbsp;<a href="#rfc.iref.d.100"><b>9.4</b></a></li><li>DAV:no-version-delete precondition&nbsp;&nbsp;<a href="#rfc.iref.d.20"><b>3.13</b></a></li><li>DAV:one-baseline-controlled-collection-per-history-per-workspace precondition&nbsp;&nbsp;<a href="#rfc.iref.d.122"><b>12.6</b></a></li><li>DAV:one-checkout-per-activity-per-history precondition&nbsp;&nbsp;<a href="#rfc.iref.d.160"><b>13.10</b></a></li><li>DAV:one-version-controlled-resource-per-history-per-workspace precondition&nbsp;&nbsp;<a href="#rfc.iref.d.68"><b>6.7</b></a></li><li>DAV:one-version-per-history-per-baseline precondition&nbsp;&nbsp;<a href="#rfc.iref.d.133"><b>12.12</b></a></li><li>DAV:predecessor-set property&nbsp;&nbsp;<a href="#rfc.section.3.3.2"><b>3.3.2</b></a>, <a href="#rfc.section.3.4.1"><b>3.4.1</b></a></li><li>DAV:preserve-versioning-properties postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.28"><b>3.15</b></a></li><li>DAV:put-under-version-control postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.2"><b>3.5</b></a></li><li>DAV:reference-version-controlled-configuration postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.124"><b>12.6</b></a></li><li>DAV:remove-label postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.77"><b>8.2</b></a></li><li>DAV:report-properties postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.71"><b>7.1</b></a>, <a href="#rfc.iref.d.114"><b>11.2</b></a></li><li>DAV:resource-must-be-null precondition&nbsp;&nbsp;<a href="#rfc.iref.d.59"><b>6.3</b></a>, <a href="#rfc.iref.d.149"><b>13.5</b></a></li><li>DAV:restore-content-and-dead-properties postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.48"><b>4.5</b></a></li><li>DAV:root-version property&nbsp;&nbsp;<a href="#rfc.section.5.1.2"><b>5.1.2</b></a></li><li>DAV:select-existing-baseline postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.125"><b>12.6</b></a></li><li>DAV:set-baseline-controlled-collection-members postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.140"><b>12.13</b></a>, <a href="#rfc.iref.d.147"><b>12.14</b></a></li><li>DAV:subactivity-set property&nbsp;&nbsp;<a href="#rfc.section.13.1.3"><b>13.1.3</b></a></li><li>DAV:subbaseline-set property&nbsp;&nbsp;<a href="#rfc.section.12.2.1"><b>12.2.1</b></a>, <a href="#rfc.section.12.3.2"><b>12.3.2</b></a></li><li>DAV:successor-set property&nbsp;&nbsp;<a href="#rfc.section.3.4.2"><b>3.4.2</b></a></li><li>DAV:supported-live-property precondition&nbsp;&nbsp;<a href="#rfc.iref.d.12"><b>3.11</b></a></li><li>DAV:supported-live-property-set property&nbsp;&nbsp;<a href="#rfc.section.3.1.4"><b>3.1.4</b></a></li><li>DAV:supported-live-propertyprecondition&nbsp;&nbsp;<a href="#rfc.iref.d.16"><b>3.12</b></a></li><li>DAV:supported-method-set property&nbsp;&nbsp;<a href="#rfc.section.3.1.3"><b>3.1.3</b></a></li><li>DAV:supported-report precondition&nbsp;&nbsp;<a href="#rfc.iref.d.4"><b>3.6</b></a></li><li>DAV:supported-report-set property&nbsp;&nbsp;<a href="#rfc.section.3.1.5"><b>3.1.5</b></a></li><li>DAV:unreserved property&nbsp;&nbsp;<a href="#rfc.section.13.3.1"><b>13.3.1</b></a></li><li>DAV:update-activity-reference postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.158"><b>13.9</b></a></li><li>DAV:update-auto-update postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.107"><b>9.7</b></a></li><li>DAV:update-checked-out-reference postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.157"><b>13.9</b></a></li><li>DAV:update-content-and-properties postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.70"><b>7.1</b></a></li><li>DAV:update-merge-set postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.113"><b>11.2</b></a></li><li>DAV:update-predecessor-set postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.22"><b>3.13</b></a></li><li>DAV:update-subbaselines postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.141"><b>12.13</b></a></li><li>DAV:update-version-controlled-collection-members postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.179"><b>14.11</b></a></li><li>DAV:update-workspace-reference postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.159"><b>13.9</b></a></li><li>DAV:version-control-working-collection-members postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.178"><b>14.10</b></a></li><li>DAV:version-controlled-binding-set property&nbsp;&nbsp;<a href="#rfc.section.14.2.1"><b>14.2.1</b></a></li><li>DAV:version-controlled-configuration property&nbsp;&nbsp;<a href="#rfc.section.12.4.1"><b>12.4.1</b></a></li><li>DAV:version-controlled-configuration-must-not-exist precondition&nbsp;&nbsp;<a href="#rfc.iref.d.119"><b>12.6</b></a></li><li>DAV:version-history property&nbsp;&nbsp;<a href="#rfc.section.5.2.1"><b>5.2.1</b></a>, <a href="#rfc.section.5.3.1"><b>5.3.1</b></a></li><li>DAV:version-history resource type&nbsp;&nbsp;<a href="#rfc.section.5.1"><b>5.1</b></a></li><li>DAV:version-history-has-root postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.54"><b>5.6</b></a></li><li>DAV:version-history-is-tree precondition&nbsp;&nbsp;<a href="#rfc.iref.d.29"><b>3.16</b></a>, <a href="#rfc.iref.d.39"><b>4.4</b></a>, <a href="#rfc.iref.d.97">9.4</a></li><li>DAV:version-name property&nbsp;&nbsp;<a href="#rfc.section.3.4.4"><b>3.4.4</b></a></li><li>DAV:version-set property&nbsp;&nbsp;<a href="#rfc.section.5.1.1"><b>5.1.1</b></a></li><li>DAV:version-tree report&nbsp;&nbsp;<a href="#rfc.section.3.7"><b>3.7</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.d.6">3.7</a></li></ul></li><li>DAV:workspace property&nbsp;&nbsp;<a href="#rfc.section.6.2.1"><b>6.2.1</b></a></li><li>DAV:workspace-checkout-set property&nbsp;&nbsp;<a href="#rfc.section.6.1.1"><b>6.1.1</b></a></li><li>DAV:workspace-location-ok precondition&nbsp;&nbsp;<a href="#rfc.iref.d.60"><b>6.3</b></a></li><li>DAV:workspace-member-moved postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.64"><b>6.6</b></a></li><li>DAV:workspace-moved postcondition&nbsp;&nbsp;<a href="#rfc.iref.d.65"><b>6.6</b></a></li><li>DELETE method&nbsp;&nbsp;<ul><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.d.21">3.13</a>, <a href="#rfc.iref.d.52">5.6</a>, <a href="#rfc.iref.d.62">6.5</a>, <a href="#rfc.iref.d.116">11.5</a>, <a href="#rfc.iref.d.155">13.8</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.d.19">3.13</a>, <a href="#rfc.iref.d.169">14.4</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.8">13.8</a></li><li>additional semantics with Merge Feature&nbsp;&nbsp;<a href="#rfc.section.11.5">11.5</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.13">3.13</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.4">14.4</a></li><li>additional semantics with Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5.6">5.6</a></li><li>additional semantics with Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6.5">6.5</a></li></ul></li><li>Descendant&nbsp;&nbsp;<a href="#rfc.iref.d.1">1.3</a></li></ul></li><li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul><li>Features&nbsp;&nbsp;<ul><li>Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13"><b>13</b></a></li><li>Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12"><b>12</b></a></li><li>Label Feature&nbsp;&nbsp;<a href="#rfc.section.8"><b>8</b></a></li><li>Merge Feature&nbsp;&nbsp;<a href="#rfc.section.11"><b>11</b></a></li><li>UPDATE Feature&nbsp;&nbsp;<a href="#rfc.section.7"><b>7</b></a></li><li>Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3"><b>3</b></a></li><li>Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14"><b>14</b></a></li><li>Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5"><b>5</b></a></li><li>Working-Resource Feature&nbsp;&nbsp;<a href="#rfc.section.9"><b>9</b></a></li><li>Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6"><b>6</b></a></li></ul></li><li>Fork&nbsp;&nbsp;<a href="#rfc.iref.f.1">1.3</a></li></ul></li><li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul><li>GET method&nbsp;&nbsp;<ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.g.1">8.5</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.g.3">8.5</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.g.2">8.5</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.5">8.5</a></li></ul></li></ul></li><li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul><li>Headers&nbsp;&nbsp;<ul><li>Label&nbsp;&nbsp;<a href="#rfc.section.8.3"><b>8.3</b></a></li></ul></li></ul></li><li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul><li><em>ISO639</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO639.1">15</a>, <a href="#ISO639"><b>20</b></a></li></ul></li><li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul><li>Label&nbsp;&nbsp;<a href="#rfc.iref.l.1">1.3</a></li><li>Label Feature&nbsp;&nbsp;<a href="#rfc.section.8"><b>8</b></a></li><li>Label header&nbsp;&nbsp;<a href="#rfc.section.8.3"><b>8.3</b></a></li><li>LABEL method&nbsp;&nbsp;<a href="#rfc.section.8.2"><b>8.2</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.l.2">8.2</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.l.4">8.2</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.l.3">8.2</a></li></ul></li></ul></li><li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul><li>Merge&nbsp;&nbsp;<a href="#rfc.iref.m.1">1.3</a></li><li>Merge Feature&nbsp;&nbsp;<a href="#rfc.section.11"><b>11</b></a></li><li>MERGE method&nbsp;&nbsp;<a href="#rfc.section.11.2"><b>11.2</b></a><ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.m.21">13.12</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.16">12.14</a>, <a href="#rfc.iref.m.22">13.12</a>, <a href="#rfc.iref.m.26">14.11</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.15">12.14</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.12">13.12</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.14">12.14</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.11">14.11</a></li><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.m.11">11.2</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.13">11.2</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.12">11.2</a></li></ul></li><li>Methods&nbsp;&nbsp;<ul><li>BASELINE-CONTROL&nbsp;&nbsp;<a href="#rfc.section.12.6"><b>12.6</b></a></li><li>CHECKIN&nbsp;&nbsp;<a href="#rfc.section.4.4"><b>4.4</b></a>, <a href="#rfc.section.9.4"><b>9.4</b></a></li><li>CHECKOUT&nbsp;&nbsp;<a href="#rfc.section.4.3"><b>4.3</b></a>, <a href="#rfc.section.8.8"><b>8.8</b></a></li><li>LABEL&nbsp;&nbsp;<a href="#rfc.section.8.2"><b>8.2</b></a></li><li>MERGE&nbsp;&nbsp;<a href="#rfc.section.11.2"><b>11.2</b></a></li><li>MKACTIVITY&nbsp;&nbsp;<a href="#rfc.section.13.5"><b>13.5</b></a></li><li>MKWORKSPACE&nbsp;&nbsp;<a href="#rfc.section.6.3"><b>6.3</b></a></li><li>REPORT&nbsp;&nbsp;<a href="#rfc.section.3.6"><b>3.6</b></a></li><li>UNCHECKOUT&nbsp;&nbsp;<a href="#rfc.section.4.5"><b>4.5</b></a></li><li>UPDATE&nbsp;&nbsp;<a href="#rfc.section.7.1"><b>7.1</b></a></li><li>VERSION-CONTROL&nbsp;&nbsp;<a href="#rfc.section.3.5"><b>3.5</b></a></li></ul></li><li>MKACTIVITY method&nbsp;&nbsp;<a href="#rfc.section.13.5"><b>13.5</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.m.17">13.5</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.19">13.5</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.18">13.5</a></li></ul></li><li>MKCOL method&nbsp;&nbsp;<ul><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.14">12.9</a>, <a href="#rfc.iref.m.24">14.5</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.23">14.5</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.9">12.9</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.5">14.5</a></li></ul></li><li>MKWORKSPACE method&nbsp;&nbsp;<a href="#rfc.section.6.3"><b>6.3</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.m.5">6.3</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.7">6.3</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.6">6.3</a></li></ul></li><li>MOVE method&nbsp;&nbsp;<ul><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.m.3">3.15</a>, <a href="#rfc.iref.m.8">6.6</a>, <a href="#rfc.iref.m.10">9.7</a>, <a href="#rfc.iref.m.20">13.9</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.m.2">3.15</a>, <a href="#rfc.iref.m.4">5.8</a>, <a href="#rfc.iref.m.9">9.7</a>, <a href="#rfc.iref.m.25">14.7</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.9">13.9</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.15">3.15</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.7">14.7</a></li><li>additional semantics with Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5.8">5.8</a></li><li>additional semantics with Working-Resource Feature&nbsp;&nbsp;<a href="#rfc.section.9.7">9.7</a></li><li>additional semantics with Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6.6">6.6</a></li></ul></li></ul></li><li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul><li>OPTIONS method&nbsp;&nbsp;<ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.o.1">5.5</a>, <a href="#rfc.iref.o.2">6.4</a>, <a href="#rfc.iref.o.3">13.7</a></li><li>additional semantics with Activity Feature&nbsp;&nbsp;<a href="#rfc.section.13.7">13.7</a></li><li>additional semantics with Additional Version-Controlled Resource Properties&nbsp;&nbsp;<a href="#rfc.section.5.5">5.5</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.8">12.8</a></li><li>additional semantics with CHECKOUT-IN-PLACE FEATURE&nbsp;&nbsp;<a href="#rfc.section.4.6">4.6</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.4">8.4</a></li><li>additional semantics with Merge Feature&nbsp;&nbsp;<a href="#rfc.section.11.4">11.4</a></li><li>additional semantics with UPDATE Feature&nbsp;&nbsp;<a href="#rfc.section.7.2">7.2</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.9">3.9</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.3">14.3</a></li><li>additional semantics with Working-Resource Feature&nbsp;&nbsp;<a href="#rfc.section.9.5">9.5</a></li><li>additional semantics with Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6.4">6.4</a></li></ul></li></ul></li><li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul><li>Predecessor&nbsp;&nbsp;<a href="#rfc.iref.p.1">1.3</a></li><li>Properties&nbsp;&nbsp;<ul><li>DAV:activity-checkout-set&nbsp;&nbsp;<a href="#rfc.section.13.1.2"><b>13.1.2</b></a></li><li>DAV:activity-set&nbsp;&nbsp;<a href="#rfc.section.13.2.1"><b>13.2.1</b></a>, <a href="#rfc.section.13.3.2"><b>13.3.2</b></a></li><li>DAV:activity-version-set&nbsp;&nbsp;<a href="#rfc.section.13.1.1"><b>13.1.1</b></a></li><li>DAV:auto-merge-set&nbsp;&nbsp;<a href="#rfc.section.11.1.2"><b>11.1.2</b></a></li><li>DAV:auto-update&nbsp;&nbsp;<a href="#rfc.section.9.2.1"><b>9.2.1</b></a></li><li>DAV:auto-version&nbsp;&nbsp;<a href="#rfc.section.3.2.2"><b>3.2.2</b></a></li><li>DAV:baseline-collection&nbsp;&nbsp;<a href="#rfc.section.12.3.1"><b>12.3.1</b></a></li><li>DAV:baseline-controlled-collection&nbsp;&nbsp;<a href="#rfc.section.12.1.1"><b>12.1.1</b></a></li><li>DAV:baseline-controlled-collection-set&nbsp;&nbsp;<a href="#rfc.section.12.5.1"><b>12.5.1</b></a></li><li>DAV:checked-in&nbsp;&nbsp;<a href="#rfc.section.3.2.1"><b>3.2.1</b></a></li><li>DAV:checked-out&nbsp;&nbsp;<a href="#rfc.section.3.3.1"><b>3.3.1</b></a></li><li>DAV:checkin-fork&nbsp;&nbsp;<a href="#rfc.section.4.1.2"><b>4.1.2</b></a>, <a href="#rfc.section.4.2.2"><b>4.2.2</b></a>, <a href="#rfc.section.9.1.2">9.1.2</a>, <a href="#rfc.section.9.2.3">9.2.3</a></li><li>DAV:checkout-fork&nbsp;&nbsp;<a href="#rfc.section.4.1.1"><b>4.1.1</b></a>, <a href="#rfc.section.4.2.1"><b>4.2.1</b></a>, <a href="#rfc.section.9.1.1">9.1.1</a>, <a href="#rfc.section.9.2.2">9.2.2</a></li><li>DAV:checkout-set&nbsp;&nbsp;<a href="#rfc.section.3.4.3"><b>3.4.3</b></a></li><li>DAV:comment&nbsp;&nbsp;<a href="#rfc.section.3.1.1"><b>3.1.1</b></a></li><li>DAV:creator-displayname&nbsp;&nbsp;<a href="#rfc.section.3.1.2"><b>3.1.2</b></a></li><li>DAV:current-activity-set&nbsp;&nbsp;<a href="#rfc.section.13.4.1"><b>13.4.1</b></a></li><li>DAV:current-workspace-set&nbsp;&nbsp;<a href="#rfc.section.13.1.4"><b>13.1.4</b></a></li><li>DAV:eclipsed-set&nbsp;&nbsp;<a href="#rfc.section.14.1.1"><b>14.1.1</b></a></li><li>DAV:label-name-set&nbsp;&nbsp;<a href="#rfc.section.8.1.1"><b>8.1.1</b></a></li><li>DAV:merge-set&nbsp;&nbsp;<a href="#rfc.section.11.1.1"><b>11.1.1</b></a></li><li>DAV:predecessor-set&nbsp;&nbsp;<a href="#rfc.section.3.3.2"><b>3.3.2</b></a>, <a href="#rfc.section.3.4.1"><b>3.4.1</b></a></li><li>DAV:root-version&nbsp;&nbsp;<a href="#rfc.section.5.1.2"><b>5.1.2</b></a></li><li>DAV:subactivity-set&nbsp;&nbsp;<a href="#rfc.section.13.1.3"><b>13.1.3</b></a></li><li>DAV:subbaseline-set&nbsp;&nbsp;<a href="#rfc.section.12.2.1"><b>12.2.1</b></a>, <a href="#rfc.section.12.3.2"><b>12.3.2</b></a></li><li>DAV:successor-set&nbsp;&nbsp;<a href="#rfc.section.3.4.2"><b>3.4.2</b></a></li><li>DAV:supported-live-property-set&nbsp;&nbsp;<a href="#rfc.section.3.1.4"><b>3.1.4</b></a></li><li>DAV:supported-method-set&nbsp;&nbsp;<a href="#rfc.section.3.1.3"><b>3.1.3</b></a></li><li>DAV:supported-report-set&nbsp;&nbsp;<a href="#rfc.section.3.1.5"><b>3.1.5</b></a></li><li>DAV:unreserved&nbsp;&nbsp;<a href="#rfc.section.13.3.1"><b>13.3.1</b></a></li><li>DAV:version-controlled-binding-set&nbsp;&nbsp;<a href="#rfc.section.14.2.1"><b>14.2.1</b></a></li><li>DAV:version-controlled-configuration&nbsp;&nbsp;<a href="#rfc.section.12.4.1"><b>12.4.1</b></a></li><li>DAV:version-history&nbsp;&nbsp;<a href="#rfc.section.5.2.1"><b>5.2.1</b></a>, <a href="#rfc.section.5.3.1"><b>5.3.1</b></a></li><li>DAV:version-name&nbsp;&nbsp;<a href="#rfc.section.3.4.4"><b>3.4.4</b></a></li><li>DAV:version-set&nbsp;&nbsp;<a href="#rfc.section.5.1.1"><b>5.1.1</b></a></li><li>DAV:workspace&nbsp;&nbsp;<a href="#rfc.section.6.2.1"><b>6.2.1</b></a></li><li>DAV:workspace-checkout-set&nbsp;&nbsp;<a href="#rfc.section.6.1.1"><b>6.1.1</b></a></li></ul></li><li>PROPFIND method&nbsp;&nbsp;<ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.p.7">8.6</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.p.6">3.12</a>, <a href="#rfc.iref.p.9">8.6</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.p.4">3.11</a>, <a href="#rfc.iref.p.8">8.6</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.6">8.6</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.11">3.11</a></li></ul></li><li>PROPPATCH method&nbsp;&nbsp;<ul><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.p.5">3.12</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.12">3.12</a></li></ul></li><li>PUT method&nbsp;&nbsp;<ul><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.p.3">3.10</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.p.2">3.10</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.10">3.10</a></li></ul></li></ul></li><li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul><li>REPORT method&nbsp;&nbsp;<a href="#rfc.section.3.6"><b>3.6</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.r.2">3.6</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.r.4">3.6</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.r.3">3.6</a></li></ul></li><li>Reports&nbsp;&nbsp;<ul><li>DAV:compare-baseline&nbsp;&nbsp;<a href="#rfc.section.12.7"><b>12.7</b></a></li><li>DAV:expand-property&nbsp;&nbsp;<a href="#rfc.section.3.8"><b>3.8</b></a></li><li>DAV:latest-activity-version&nbsp;&nbsp;<a href="#rfc.section.13.6"><b>13.6</b></a></li><li>DAV:locate-by-history&nbsp;&nbsp;<a href="#rfc.section.5.4"><b>5.4</b></a></li><li>DAV:merge-preview&nbsp;&nbsp;<a href="#rfc.section.11.3"><b>11.3</b></a></li><li>DAV:version-tree&nbsp;&nbsp;<a href="#rfc.section.3.7"><b>3.7</b></a></li></ul></li><li>Resource Types&nbsp;&nbsp;<ul><li>DAV:activity&nbsp;&nbsp;<a href="#rfc.section.13.1"><b>13.1</b></a></li><li>DAV:baseline&nbsp;&nbsp;<a href="#rfc.section.12.3"><b>12.3</b></a></li><li>DAV:version-history&nbsp;&nbsp;<a href="#rfc.section.5.1"><b>5.1</b></a></li></ul></li><li><em>RFC2026</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2026.1">18</a>, <a href="#rfc.xref.RFC2026.2">18</a>, <a href="#RFC2026"><b>20</b></a><ul><li><em>Section 10.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2026.2">18</a></li></ul></li><li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>20</b></a></li><li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">15</a>, <a href="#RFC2277"><b>20</b></a></li><li><em>RFC2279</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2279.1">15</a>, <a href="#RFC2279"><b>20</b></a></li><li><em>RFC2396</em>&nbsp;&nbsp;<a href="#RFC2396"><b>20</b></a></li><li><em>RFC2518</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.1">1.1</a>, <a href="#rfc.xref.RFC2518.2">1.4.5</a>, <a href="#rfc.xref.RFC2518.3">1.7</a>, <a href="#rfc.xref.RFC2518.4">3.7</a>, <a href="#rfc.xref.RFC2518.5">3.7</a>, <a href="#rfc.xref.RFC2518.6">3.8</a>, <a href="#rfc.xref.RFC2518.7">5.4</a>, <a href="#rfc.xref.RFC2518.8">7.1</a>, <a href="#rfc.xref.RFC2518.9">7.1</a>, <a href="#rfc.xref.RFC2518.10">11.2</a>, <a href="#rfc.xref.RFC2518.11">11.2</a>, <a href="#rfc.xref.RFC2518.12">15</a>, <a href="#rfc.xref.RFC2518.13">16</a>, <a href="#RFC2518"><b>20</b></a>, <a href="#rfc.xref.RFC2518.14">A.1</a>, <a href="#rfc.xref.RFC2518.15">A.2</a>, <a href="#rfc.xref.RFC2518.16">A.2</a><ul><li><em>Section 8.8.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.3">1.7</a></li><li><em>Section 12.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.2">1.4.5</a></li><li><em>Section 12.9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.5">3.7</a>, <a href="#rfc.xref.RFC2518.6">3.8</a>, <a href="#rfc.xref.RFC2518.9">7.1</a>, <a href="#rfc.xref.RFC2518.11">11.2</a></li><li><em>Section 12.11</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.4">3.7</a>, <a href="#rfc.xref.RFC2518.7">5.4</a>, <a href="#rfc.xref.RFC2518.8">7.1</a>, <a href="#rfc.xref.RFC2518.10">11.2</a></li><li><em>Section 16</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.12">15</a></li><li><em>Section 17</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2518.13">16</a></li></ul></li><li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1.1</a>, <a href="#RFC2616"><b>20</b></a>, <a href="#rfc.xref.RFC2616.2">A.1</a>, <a href="#rfc.xref.RFC2616.3">A.2</a></li><li><em>RFC3023</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3023.1">15</a>, <a href="#RFC3023"><b>20</b></a></li><li><em>RFC3066</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3066.1">15</a>, <a href="#RFC3066"><b>20</b></a></li><li>Root Version Resource&nbsp;&nbsp;<a href="#rfc.iref.r.1">1.3</a></li></ul></li><li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul><li>Successor&nbsp;&nbsp;<a href="#rfc.iref.s.1">1.3</a></li></ul></li><li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul><li>UNCHECKOUT method&nbsp;&nbsp;<a href="#rfc.section.4.5"><b>4.5</b></a><ul><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.u.3">4.5</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.u.5">4.5</a></li><li>Preconditions&nbsp;&nbsp;<a href="#rfc.iref.u.4">4.5</a></li></ul></li><li>UNLOCK method&nbsp;&nbsp;<ul><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.u.2">3.16</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.u.1">3.16</a></li><li>additional semantics with Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3.16">3.16</a></li></ul></li><li>UPDATE Feature&nbsp;&nbsp;<a href="#rfc.section.7"><b>7</b></a></li><li>UPDATE method&nbsp;&nbsp;<a href="#rfc.section.7.1"><b>7.1</b></a><ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.u.8">8.9</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.u.10">8.9</a>, <a href="#rfc.iref.u.12">12.13</a>, <a href="#rfc.iref.u.13">14.11</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.u.9">8.9</a>, <a href="#rfc.iref.u.11">12.13</a></li><li>additional semantics with Baseline Feature&nbsp;&nbsp;<a href="#rfc.section.12.13">12.13</a></li><li>additional semantics with Label Feature&nbsp;&nbsp;<a href="#rfc.section.8.9">8.9</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.11">14.11</a></li><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.u.6">7.1</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.u.7">7.1</a></li></ul></li></ul></li><li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul><li>Version Control&nbsp;&nbsp;<a href="#rfc.iref.v.1">1.3</a></li><li>Version History Resource&nbsp;&nbsp;<a href="#rfc.iref.v.5">1.3</a></li><li>Version Name&nbsp;&nbsp;<a href="#rfc.iref.v.6">1.3</a></li><li>Version Resource&nbsp;&nbsp;<a href="#rfc.iref.v.4">1.3</a></li><li>Version-Control Feature&nbsp;&nbsp;<a href="#rfc.section.3"><b>3</b></a></li><li>VERSION-CONTROL method&nbsp;&nbsp;<a href="#rfc.section.3.5"><b>3.5</b></a><ul><li>Additional Marshalling&nbsp;&nbsp;<a href="#rfc.iref.v.10">6.7</a></li><li>Additional Postconditions&nbsp;&nbsp;<a href="#rfc.iref.v.9">5.9</a>, <a href="#rfc.iref.v.12">6.7</a>, <a href="#rfc.iref.v.15">14.8</a></li><li>Additional Preconditions&nbsp;&nbsp;<a href="#rfc.iref.v.11">6.7</a>, <a href="#rfc.iref.v.14">14.8</a></li><li>additional semantics with Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14.8">14.8</a></li><li>additional semantics with Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5.9">5.9</a></li><li>additional semantics with Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6.7">6.7</a></li><li>Marshalling&nbsp;&nbsp;<a href="#rfc.iref.v.7">3.5</a></li><li>Postconditions&nbsp;&nbsp;<a href="#rfc.iref.v.8">3.5</a></li></ul></li><li>Version-Controlled Configuration Resource&nbsp;&nbsp;<a href="#rfc.iref.v.13">10.2</a></li><li>Version-Controlled Resource&nbsp;&nbsp;<a href="#rfc.iref.v.3">1.3</a></li><li>Version-Controlled-Collection Feature&nbsp;&nbsp;<a href="#rfc.section.14"><b>14</b></a></li><li>Version-History Feature&nbsp;&nbsp;<a href="#rfc.section.5"><b>5</b></a></li><li>Versionable Resource&nbsp;&nbsp;<a href="#rfc.iref.v.2">1.3</a></li></ul></li><li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul><li>Working Resource&nbsp;&nbsp;<a href="#rfc.iref.w.2">1.3</a></li><li>Working-Resource Feature&nbsp;&nbsp;<a href="#rfc.section.9"><b>9</b></a></li><li>Workspace Feature&nbsp;&nbsp;<a href="#rfc.section.6"><b>6</b></a></li><li>Workspace Resource&nbsp;&nbsp;<a href="#rfc.iref.w.1">1.3</a></li></ul></li></ul></div></section><hr class="noprint"><section id="rfc.authors" class="np"><h2><a href="#rfc.authors">Authors' Addresses</a></h2><address><b>Geoffrey Clemm</b><br>Rational Software<br>20 Maguire Road<br>Lexington, MA&nbsp;02421<br>US<br>EMail: <a href="mailto:geoffrey.clemm@rational.com">geoffrey.clemm@rational.com</a></address><address><b>Jim Amsden</b><br>IBM<br>3039 Cornwallis<br>Research Triangle Park<br>NC&nbsp;27709<br>US<br>EMail: <a href="mailto:jamsden@us.ibm.com">jamsden@us.ibm.com</a></address><address><b>Tim Ellison</b><br>IBM<br>Hursley Park<br>Winchester, S021 2JN<br>UK<br>EMail: <a href="mailto:tim_ellison@uk.ibm.com">tim_ellison@uk.ibm.com</a></address><address><b>Christopher Kaler</b><br>Microsoft<br>One Microsoft Way<br>Redmond, WA&nbsp;90852<br>US<br>EMail: <a href="mailto:ckaler@microsoft.com">ckaler@microsoft.com</a></address><address><b>Jim Whitehead</b><br>UC Santa Cruz, Dept. of Computer Science<br>1156 High Street<br>Santa Cruz, CA&nbsp;95064<br>US<br>EMail: <a href="mailto:ejw@cse.ucsc.edu">ejw@cse.ucsc.edu</a></address></section><section id="rfc.copyright"><h2><a href="#rfc.copyright">Full Copyright Statement</a></h2><p>Copyright © The Internet Society (2002). All Rights Reserved.</p><p>This
 document and translations of it may be copied and furnished to others, 
and derivative works that comment on or otherwise explain it or assist 
in its implementation may be prepared, copied, published and 
distributed, in whole or in part, without restriction of any kind, 
provided that the above copyright notice and this paragraph are included
 on all such copies and derivative works. However, this document itself 
may not be modified in any way, such as by removing the copyright notice
 or references to the Internet Society or other Internet organizations, 
except as needed for the purpose of developing Internet standards in 
which case the procedures for copyrights defined in the Internet 
Standards process must be followed, or as required to translate it into 
languages other than English.</p><p>The limited permissions granted 
above are perpetual and will not be revoked by the Internet Society or 
its successors or assigns.</p><p>This document and the information 
contained herein is provided on an “AS IS” basis and THE INTERNET 
SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL 
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 
PARTICULAR PURPOSE.</p></section><section id="rfc.ipr"><h2><a href="#rfc.ipr">Intellectual Property</a></h2><p>The
 IETF takes no position regarding the validity or scope of any 
intellectual property or other rights that might be claimed to pertain 
to the implementation or use of the technology described in this 
document or the extent to which any license under such rights might or 
might not be available; neither does it represent that it has made any 
effort to identify any such rights. Information on the IETF's procedures
 with respect to rights in standards-track and standards-related 
documentation can be found in BCP-11. Copies of claims of rights made 
available for publication and any assurances of licenses to be made 
available, or the result of an attempt made to obtain a general license 
or permission for the use of such proprietary rights by implementors or 
users of this specification can be obtained from the IETF Secretariat.</p><p>The
 IETF invites any interested party to bring to its attention any 
copyrights, patents or patent applications, or other proprietary rights 
which may cover technology that may be required to practice this 
standard. Please address the information to the IETF Executive Director.</p></section><section id="n-acknowledgment"><h2><a href="#n-acknowledgment">Acknowledgment</a></h2><p>Funding for the RFC Editor function is currently provided by the Internet Society.</p></section>
</body></html>